Jonathan Tan <jonathantanmy@xxxxxxxxxx> writes: > At $DAY_JOB, we've noticed some pushes being larger than necessary. > Here's a first step towards solving that. In this protocol change, we're > allowing the user to specify an ancestor believed to be common Is this designed to be a short-term kludge until we have a similar "common discovery" negotiation we have on the upload-pack side, or do we know some fundamental reason why the "push" side cannot do so? Just being curious as to what the eventual and ideal future beyond "we must have an immediate problem worked around in some way even with an ugly hack before the end of this cycle" would be. Will take a look but not today. Thanks.
