From: Daniel Barkalow <barkalow@iabervon.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] Define relative .git/objects/info/alternates semantics.
Date: Tue, 13 Sep 2005 12:31:38 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0509131224290.23242@iabervon.org> (raw)
In-Reply-To: <7vk6hl4fd9.fsf_-_@assigned-by-dhcp.cox.net>
On Tue, 13 Sep 2005, Junio C Hamano wrote:
> Linus Torvalds <torvalds@osdl.org> writes:
>
> > Yes. We should probably have some well-defined meaning for relative paths
> > in there regardless (eg just define that they are always relative to the
> > main GIT_OBJECT_DIRECTORY or something).
> >
> > That would also allow mirrors to mirror the git archives in different
> > places, without upsetting the result (as long as they are mirrored
> > together).
> >
> > Linus
>
> This patch is request-for-comments. I have experimented it and
> have a feeling that it may be more intuitive to make it relative
> to $project.git/ directory, instead of $project.git/objects as
> you originally suggested, in which case a maintainer tree would
> have "../../torvalds/linux-2.6.git/objects" instead (one less
> dotdot), and if nobody objects that is probably what I'll end up
> doing.
It seems odd to have the "objects" at the end and not be starting from
"objects". I suspect that the most intuitive thing would be for something
under $project.git/info to be .git to .git, while something under
.git/objects/info should be objects to objects.
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2005-09-13 16:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3mzmjvbh7.fsf@telia.com>
[not found] ` <Pine.LNX.4.58.0509110908590.4912@g5.osdl.org>
[not found] ` <20050911185711.GA22556@mars.ravnborg.org>
2005-09-11 19:06 ` What's up with the GIT archive on www.kernel.org? Linus Torvalds
2005-09-11 19:46 ` Sam Ravnborg
2005-09-11 19:56 ` Linus Torvalds
2005-09-11 21:09 ` Roland Dreier
2005-09-11 21:24 ` Linus Torvalds
2005-09-11 21:33 ` Linus Torvalds
2005-09-12 1:39 ` Junio C Hamano
2005-09-12 2:45 ` Dmitry Torokhov
2005-09-12 18:42 ` Ryan Anderson
2005-09-12 3:39 ` Linus Torvalds
2005-09-13 7:05 ` [PATCH] Define relative .git/objects/info/alternates semantics Junio C Hamano
2005-09-13 16:22 ` Linus Torvalds
2005-09-13 17:30 ` Junio C Hamano
2005-09-13 16:31 ` Daniel Barkalow [this message]
2005-09-12 17:10 ` What's up with the GIT archive on www.kernel.org? H. Peter Anvin
2005-09-12 18:22 ` Tony Luck
2005-09-12 18:37 ` Linus Torvalds
2005-09-11 20:08 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.63.0509131224290.23242@iabervon.org \
--to=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).