On Sun, 9 Sep 2007, Shawn O. Pearce wrote:

quoted text
>  Originally I started this patch out thinking that --no-thin was
>  the default for git-push and that therefore this was almost a
>  no-brainer change.  Then I found out it isn't the default, so now
>  I'm not so sure about the value of this particular patch.

How come it isn't the default?

Last time I fiddled in that area, I explicitly avoided enabling thin 
packs on push for the following reasons:

1) pushes happen less often than fetches, so the bandwidth saving is 
   much less visible in that case overall.

2) thin packs have to be complemented with missing delta bases to be 
   valid, so many received thin packs will take more disk space.

3) the bother of repacking should be distributed amongst "clients" 
   i.e. fetchers and pushers as much as possible, and not the server
   being fetched or pushed, to keep disk and CPU usage low on the 
   server.

This is why a fetch should get thin packs but a push should not.



Nicolas
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html