Caleb Gray <hey@xxxxxxxxxxxxx> writes: > To Clarify: I'm talking about a server-side only cache which behaves > much like a `tar` file: it is a flat version of exactly(*) what ends > up on the client's storage. When a client runs `git --clone` and > there's a valid cache on the other end, that's all that gets streamed. So this is to save server processing time only. It does not save bandwidth (the "cache" is bit-for-bit idential replay of the clone request it served earlier), and it does not save client processing cycles (as the receiving end must validate the whole packdata it received before it can even know what objects it received). OK.
