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

From: Shawn Pearce <spearce@spearce.org>
Date: Mar 1, 2006, 17:28 UTC
Message-ID: <20060301172816.GA4090@spearce.org>
In-Reply-To: <200603011814.43573.Josef.Weidendorfer@gmx.de>

Josef Weidendorfer <Josef.Weidendorfer@gmx.de> wrote:

Show 23 quoted lines

> On Wednesday 01 March 2006 17:24, Linus Torvalds wrote:
> > 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.

This is a really good idea. It certainly would prevent polluting the heads namespace. And its a lot easier to explain to someone than the mapping in the Pull line usually is.

-- 
Shawn.