Re: git-svn and huge data and modifying the git-svn-HEAD branch directly
- From
Linus Torvalds <torvalds@osdl.org>
- Date
- Mar 1, 2006, 16:24 UTC
- Message-ID
- <Pine.LNX.4.64.0603010821590.22647@g5.osdl.org>
- In-Reply-To
- <4405C6BE.2000706@op5.se>
On Wed, 1 Mar 2006, Andreas Ericsson wrote:
Show 9 quoted lines
> > Personally I'm all for namespace separation. I'm assuming the script has the > tracker-branch hardcoded anyway, so I don't really understand why it would be > necessary to keep other refs in a separate directory and, if it *is* > necessary, why that subdirectory can't be .git/refs/heads/svn. > > Eric mentioned earlier that the tracking-branch can't be committed to (ever), > so the user convenience for searching other directories should be nearly > non-existant.
The thing about it being .git/refs/heads/svn/xyzzy is that then you can do
git checkout svn/xyzzy
and start modifying it. Which is exactly against the point: the thing is _not_ a branch and you must _not_ commit to it.
It's much more like a tag: it's a pointer to the last point of an svn-import.
So I think it should either _be_ a tag (although Dscho worries about some broken porcelain being confused by tags changing) or it should be in a namespace all it's own. Not under .git/refs/heads/ at any point, because it is _not_ a head of development.
Linus