Re: [PATCH] fetch-pack: do not reset in_vain on non-novel acks

Jonathan Tan writes: > The MAX_IN_VAIN mechanism was introduced in commit f061e5f ("fetch-pack: > give up after getting too many "ack continue"", 2006-05-24) to stop ref > negotiation if a number of consecutive "have"s have been sent with no > corresponding new acks. A

[PATCH] fetch-pack: do not reset in_vain on non-novel acks

The MAX_IN_VAIN mechanism was introduced in commit f061e5f ("fetch-pack: give up after getting too many "ack continue"", 2006-05-24) to stop ref negotiation if a number of consecutive "have"s have been sent with no corresponding new acks. A use case (as described in that commit) is the scenario in