Re: Performance issue: initial git clone causes massive repack

From: Matthieu Moy <matthieu.moy@imag.fr>
Date: Apr 6, 2009, 11:22 UTC
Message-ID: <vpq3acm6n7p.fsf@bauges.imag.fr>
In-Reply-To: <alpine.LFD.2.00.0904052326090.6741@xanadu.home>

Nicolas Pitre <nico@cam.org> writes:

> If for example you have a single pack because your repo is already fully 
> packed, then the "packing operation" involved during a clone should 
> merely copy the existing pack over with no further attempt at delta 
> compression.

There's still the question if your repository has too many objects (for example, a branch that you deleted without garbage-collecting it). Then, sending the whole pack sends data that one may have considered as "secret".

To me, this is a non-issue (if the content of these objects are secret, then why are they here at all on a public server?), but I think there were discussions here about it (can't find the right keywords to dig the archives though), and other people may think differently.

Jeff King's answer in <20090405195714.GA4716@coredump.intra.peff.net> tackles this problem too.

-- 
Matthieu