Thread (7 messages) 7 messages, 4 authors, 2016-06-15

Re: Multi-threaded 'git clone'

From: Jeff King <hidden>
Date: 2016-06-15 23:03:50

On Tue, Feb 17, 2015 at 06:16:39AM +0700, Duy Nguyen wrote:
On Mon, Feb 16, 2015 at 10:47 PM, Jeff King [off-list ref] wrote:
quoted
Each clone generates the pack on the fly
based on what's on disk and streams it out. It should _usually_ be the
same, but there's nothing to guarantee byte-for-byte equality between
invocations.
It's usually _not_ the same. I tried when I wanted to produce stable
packs. The first condition is single-threaded pack-objects. Otherwise
thread scheduler could make object order unpredictable.
True. If you keep your server repositories fully packed, that eliminates
the delta search (and/or makes it feasible to turn pack.threads to 1 to
make it deterministic). But any change in the repository (e.g., somebody
else pushing, even to a ref you are not fetching) can cause unexpected
changes in the bytes.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help