Re: git-svn and huge data and modifying the git-svn-HEAD branch directly

From: Eric Wong <normalperson@yhbt.net>
Date: Mar 1, 2006, 06:51 UTC
Message-ID: <20060301065138.GC21684@hand.yhbt.net>
In-Reply-To: <Pine.LNX.4.64.0602271634410.22647@g5.osdl.org>

Linus Torvalds <torvalds@osdl.org> wrote:

Show 14 quoted lines

> 
> 
> On Tue, 28 Feb 2006, Martin Langhoff wrote:
> > 
> > git-svn-HEAD "moves" so it's really a bad idea to have it as a tag.
> > Nothing within core git prevents it from moving, but I think that
> > porcelains will start breaking. Tags and heads are the same thing,
> > except that heads are expected to change (specifically, to move
> > forward), and tags are expected to stand still.
> <snipped>
> Using a "refs/remotes" subdirectory makes tons of sense for something like 
> this. Or something even more specific, like "refs/svn-tracking/". Git 
> shouldn't care - all the tools _should_ work fine with any subdirectory 
> structure.

Git tools only work as long as the 'refs/{remotes,svn-tracking,...}/'
prefix is specified.  git-svn-HEAD (or any $GIT_SVN_ID-HEAD) does get
specified from the command-line quite often:
	
	git checkout -b mine git-svn-HEAD
	git-log git-svn-HEAD..head
	git-svn commit git-svn-HEAD..mine
	git-log mine..git-svn-HEAD

Should rev-parse be taught to be less strict and look for basenames that can't be found in heads/ and tags/ in other directories?

-- 
Eric Wong