This is regarding the packfile negotiation in fetch-pack. If there is a concern that MAX_IN_VAIN would be hit too early (as a consequence of the patch below), I'm currently investigating the possibility of improving the negotiation ability of the client side further (for example, by prioritizing refs or heads instead of merely prioritizing by date in the priority queue of objects), but I thought I'd send the patch out first anyway to see what others think.
Jonathan Tan (1): fetch-pack: do not reset in_vain on non-novel acks fetch-pack.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) -- 2.8.0.rc3.226.g39d4020
