From: "Michal Suchánek" <msuchanek@suse.de>
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 12:05:28 +0200 [thread overview]
Message-ID: <20200520100528.GV25173@kitsune.suse.cz> (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.
What git version? Should be fixed in git 2.26.2 in SUSE and git 2.26.3
upstream.
Thanks
Michal
next prev parent reply other threads:[~2020-05-20 10:05 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 [this message]
2020-05-20 10:34 ` Andreas Schwab
2020-05-20 19:40 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200520100528.GV25173@kitsune.suse.cz \
--to=msuchanek@suse.de \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.