Re: "git-send-pack"

From: Jan Harkes <jaharkes@cs.cmu.edu>
Date: Jul 1, 2005, 14:43 UTC
Message-ID: <20050701144327.GF4821@delft.aura.cs.cmu.edu>
In-Reply-To: <pan.2005.07.01.10.31.53.906759@smurf.noris.de>

On Fri, Jul 01, 2005 at 12:31:53PM +0200, Matthias Urlichs wrote:

Show 12 quoted lines

> > In the end, it might be that the right thing to do for git on kernel.org 
> > is to have a single, unified object store which isn't accessible by 
> > anything other than git-specific protocols.
> 
> Makes sense.
> 
> >  There would have to be some 
> > way of dealing with, for example, conflicting tags that apply to 
> > different repositories, though.
>
> It seems that user-specific subdirectories in refs/heads (and, presumably,
> ../tags) mostly work already.

They work pretty well, the core git commands have no problem with them and I just sent off some patches for gitweb and gitk.

All git/objects directories can be merged into a common repository. The refs/heads and refs/tags be copied to user specific subdirectories.

Then a pull like,
    git pull http://www.kernel.org/.../torvalds/linux-2.6.git

Would become,
    git pull http://www.kernel.org/.../linux-2.6.git torvalds/linux-2.6/master

It would make rsync more expensive for people who are interested in only a branch or two, but there is only one repository which should be easier on the mirrors. The http, ssh, and some future 'pack' transfer methods won't see a difference since they only pull the specific commits they need to catch up with a branch.

Jan