Re: git-svn and huge data and modifying the git-svn-HEAD branch directly
- From
Linus Torvalds <torvalds@osdl.org>
- Date
- Mar 1, 2006, 21:28 UTC
- Message-ID
- <Pine.LNX.4.64.0603011325120.22647@g5.osdl.org>
- In-Reply-To
- <200603012126.30797.Josef.Weidendorfer@gmx.de>
On Wed, 1 Mar 2006, Josef Weidendorfer wrote:
> > So the get_sha1() magic should map "origin" to "remote/origin/master" (or instead > hardcoded master the remote branch from the first "Pull:" line) ?
Right.
> The ambiguity here would be that shortcut names of remote repositories should not be > used as tag or head names...
Well, it's not so much an ambiguity, since we'd always try tags and heads first. So it's just a fallback, the same way the short SHA1 hash is a fallback.
> I think a big plus of this would be that gitk can show branches tracking remote ones > with another color.
Yes. And with a meaningful name.
> To be able to say "git log origin.." you need the above magic, too.
It would all come automagically from just extending get_sha1().
(Actually, technically you'd put it at the end of "get_sha1_basic()")
Linus