Hi, On Thu, 17 Aug 2006, Johannes Schindelin wrote: > However, I see some real problems when a public repository has a pack like > this: if the client is older, the server has to do some real work, > especially in the case of a fresh clone. It gets even worse with a public > HTTP repo. > > The obvious short-time solution would be to make this opt-in, and use it > only on private repositories. > > Then, one could think about how to handle the delta-chains in the pack > protocol (it should be easy, since you just have to store one object > instead of a few), and make this a "supports" option. Oh, and I completely forgot: IIUC you have to unpack the (possibly big) delta-chain until you have the delta you really want, right? So, you might want to have a clever mechanism to keep the delta-chains short for recent objects (i.e. objects you are likely to need more often). At least, the delta-chains should be limited by size (_not_ by number of deltas: you can have huge deltas, and if you have to unpack 5 huge deltas before getting to the huge delta you really need, it takes really long). Ciao, Dscho - 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