"Robin H. Johnson" <robbat2@xxxxxxxxxx> wrote: > > > The GSoC 2009 ideas contain a potential project for caching the > > > generated packs, which, while having value in itself, could be partially > > > avoided by sending suitable pre-built packs (if they exist) without any > > > repacking. > > Right. It could be an option to wait and see if the GSoC gives > > something. > > How hard is it to just look at the git-upload-pack code and make it > realize that it doesn't need to repack at all for this case. I don't need to go look. I know that code. Its harder than you think. I'll tell you what, *you* go look at the git-upload-pack code and come back with a patch that doesn't need to repack at all for this case, *and* which Junio will actually apply. If its any good, Junio would apply it pretty quickly. Nobody else has managed to create such a patch just yet. Because its extremely non-trivial. Its pretty much never the case that an active repository is fully repacked, so we always have to enumerate some number of loose objects and put them into a single outgoing pack for the network. Its also considered to be a security feature of Git that we only transmit reachable objects. -- Shawn. -- 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