From: Jeff King <peff@peff.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Jonathan Tan <jonathantanmy@google.com>,
git@vger.kernel.org
Subject: Re: Fetching 24 Linux commits = 1.2 GiB
Date: Wed, 20 May 2020 15:40:19 -0400 [thread overview]
Message-ID: <20200520194019.GA340985@coredump.intra.peff.net> (raw)
In-Reply-To: <87sgfvq967.fsf@igel.home>
On Wed, May 20, 2020 at 10:53:36AM +0200, Andreas Schwab wrote:
> 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
next prev parent reply other threads:[~2020-05-20 19:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 8:01 Fetching 24 Linux commits = 1.2 GiB Jiri Slaby
2020-04-15 8:11 ` Andreas Schwab
2020-04-15 8:16 ` Jiri Slaby
2020-04-15 8:23 ` Andreas Schwab
2020-04-15 8:27 ` Jiri Slaby
2020-04-15 8:34 ` Andreas Schwab
2020-04-15 10:52 ` Kevin Daudt
2020-04-15 13:56 ` Konstantin Ryabitsev
2020-04-15 15:08 ` Junio C Hamano
2020-04-15 15:16 ` Jeff King
2020-04-15 18:52 ` Jonathan Nieder
2020-05-20 8:53 ` Andreas Schwab
2020-05-20 8:57 ` Andreas Schwab
2020-05-20 10:05 ` Michal Suchánek
2020-05-20 10:34 ` Andreas Schwab
2020-05-20 19:40 ` Jeff King [this message]
2020-05-25 18:22 ` Lukas Wunner
2020-05-25 18:37 ` Junio C Hamano
2020-04-16 6:31 ` Jiri Slaby
2020-04-21 10:02 ` Martin Wilck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200520194019.GA340985@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).