On Sun, 5 Apr 2009, Junio C Hamano wrote: > Nicolas Pitre <nico@xxxxxxx> writes: > > > What git-pack-objects does in this case is not a full repack. It > > instead _reuse_ as much of the existing packs as possible, and only does > > the heavy packing processing for loose objects and/or inter pack > > boundaryes when gluing everything together for streaming over the net. > > 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. > > One possibile scenario that you still need to spend memory and cycle is if > the cloned repository was packed to an excessive depth to cause many of > its objects to be in deltified form on insanely deep chains, while cloning > send-pack uses a depth that is more reasonable. Then pack-objects invoked > by send-pack is not allowed to reuse most of the objects and would end up > redoing the delta on them. Nope. When pack data is reused, there is simply no consideration what so ever for the actual delta depth limit. Only when an object already being used as a delta base for reused deltas is itself subject to delta compression does the real depth of the concerned delta chain is evaluated in order to not purposely bust the specified delta depth limit (otherwise a delta chain could grow unbounded). Nicolas -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html