Re: Fetching 24 Linux commits = 1.2 GiB
- From
Jeff King <peff@peff.net>
- Date
- May 20, 2020, 19:40 UTC
- Message-ID
- <20200520194019.GA340985@coredump.intra.peff.net>
- In-Reply-To
- <87sgfvq967.fsf@igel.home>
On Wed, May 20, 2020 at 10:53:36AM +0200, Andreas Schwab wrote:
Show 9 quoted lines
> On Apr 15 2020, Junio C Hamano wrote: > > > Do these (and I think we saw other reports) make us rethink the > > status of protocol v2 as the default? Are all of these fallouts > > we saw so far easy-to-fix bugs, or are there more fundamental issues > > in the v2 protocol design? > > I'm now seeing the issue myself, and can provide a backup of the > offending repository.
The "too big fetch" issue has since been fixed in "master", as well as reverting the switch to the v2 protocol (which I think is just belt-and-suspenders; AFAIK there are no known issues after the fix). Both will be in v2.27. I don't see anything on "maint", but they _could_ be part of an eventual v2.26.3.
The fix was merged in 0b07eecf6e (Merge branch 'jt/v2-fetch-nego-fix', 2020-05-01) for reference.
-Peff