Re: git-svn and huge data and modifying the git-svn-HEAD branch directly
- From
- Josef Weidendorfer <josef.weidendorfer@gmx.de>
- Date
- Mar 1, 2006, 17:14 UTC
- Message-ID
- <200603011814.43573.Josef.Weidendorfer@gmx.de>
- In-Reply-To
- <Pine.LNX.4.64.0603010821590.22647@g5.osdl.org>
On Wednesday 01 March 2006 17:24, Linus Torvalds wrote:
Show 9 quoted lines
> 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.
Isn't it the same with tracked branches of a remote git repo? With this reasoning, all heads that git-clone clones aside from the special "master" should not be under .git/refs/heads, but better under .git/refs/remotes/<remoteRepoName>/ ?
<remoteRepoName> is "origin" in the case of git-clone, so .git/remotes/origin would contain URL: http://host/repo.git Pull: master:remotes/origin/master
Then there would not be the need for the confusing special branch "origin" after cloning, as namespaces are separate.
Josef