Re: Proper Publishing of a Repository

From: Junio C Hamano <junkio@cox.net>
Date: Mar 22, 2006, 20:47 UTC
Message-ID: <7v3bha8awl.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <1143059181.4527.162.camel@cashmere.sps.mot.com>

Jon Loeliger <jdl@freescale.com> writes:

Show 10 quoted lines

> On Wed, 2006-03-22 at 14:16, Timo Hirvonen wrote:
>> Jon Loeliger <jdl@freescale.com> wrote:
>>
>> > All this on the linux kernel over HTTP.
>> 
>> Use git:// protocol (git-daemon) if possible.  It is much faster.
>
> Trust me, if it were an option, I would.  It isn't.
>
> So, I think git-prune-packed was the answer here...

It really depends on who your audiences are. By packing everything in a single pack, you are optimizing for the initial cloners but punishing incremental updaters.

Since your tree is derived from Linus tree, anybody who is interested in your tree is very likely nterested in Linus tree and chances are that she has a recent copy of it locally. In such a case, I would not be surprised if:

	$ git clone -l -s -n /local-linux-2.6.git/ jdl-linux.git
        $ cd jdl-linux.git
        $ git fetch http://jdl.com/jdl-linux.git master:refs/heads/jdl

goes a lot faster if you have loose objects around in the repository.