From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Define relative .git/objects/info/alternates semantics.
Date: Tue, 13 Sep 2005 10:30:13 -0700 [thread overview]
Message-ID: <7vvf143mfu.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0509130918170.3351@g5.osdl.org> (Linus Torvalds's message of "Tue, 13 Sep 2005 09:22:42 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> Which means that the _same_ "alternates" file can be shared with many
> different project.git/ directories, and thus it's not well-defined to make
> it relative to GIT_DIR.
Good point.
> You can make it relative to "GIT_OBJECTS_DIR/.." of course, which in most
> cases is the same thing as "GIT_DIR".
Again, good point.
next prev parent reply other threads:[~2005-09-13 17:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 16:02 What's up with the GIT archive on www.kernel.org? Peter Osterlund
2005-09-11 16:12 ` Linus Torvalds
2005-09-11 18:57 ` Sam Ravnborg
2005-09-11 19:06 ` 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 [this message]
2005-09-13 16:31 ` Daniel Barkalow
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
2005-09-11 22:12 ` Andrew Morton
2005-09-11 22:49 ` Alex Riesen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vvf143mfu.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.