Re: [PATCH] Revert "fetch: default to protocol version 2"
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Apr 22, 2020, 18:23 UTC
- Message-ID
- <xmqqtv1bidlu.fsf@gitster.c.googlers.com>
- In-Reply-To
- <20200422155047.GB91734@google.com>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 12 quoted lines
> This reverts commit 684ceae32dae726c6a5c693b257b156926aba8b7. > > Users fetching from linux-next and other kernel remotes are reporting > that the limited ref advertisement causes negotiation to reach > MAX_IN_VAIN, resulting in too-large fetches. > > Reported-by: Lubomir Rintel <lkundrak@v3.sk> > Reported-by: "Dixit, Ashutosh" <ashutosh.dixit@intel.com> > Reported-by: Jiri Slaby <jslaby@suse.cz> > Reported-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org> > Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> > ---
With the one-liner fix for resetting the "we haven't heard an Ack" timer, I am no longer so worried by hurting users by keeping them on v2 by default, but it will take some time for the fix to trickle down from the 'master' track to a maintenance release, so I am OK to apply this patch in the meantime. But let's flip the default back to v2 after the one-liner fix lands to see if (1) the fix truly helps and (2) people hit other issues in the difference between v0 and v2.
Thanks.