Thread (20 messages) flat view 20 messages, 7 authors, 2016-06-15

Re: "git-send-pack"

From: Jan Harkes <jaharkes@cs.cmu.edu>
Date: 2016-06-15 22:42:01

On Fri, Jul 01, 2005 at 12:31:53PM +0200, Matthias Urlichs wrote:
quoted
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.
quoted
 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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help