Re: clone breaks replace

Jonathan Nieder [off-list ref] writes:

Therefore if you want clients to be able to choose between a minimal
history and a larger one to save bandwidth, it has to work like this

 - to get the minimal history, fetch _without_ any replacement refs
 - to get the full history, fetch the replacement refs on top of that.

because an additional reference can only increase the number of
objects to be downloaded.

Very nicely and clearly put.  Can we have this somewhere in the docs?