From: Jeff King <peff@peff.net>
To: Evan Miller <emmiller@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Exit code 255 after large clone (32-bit PowerPC)
Date: Tue, 27 Jul 2021 08:44:40 -0400 [thread overview]
Message-ID: <YP//uBa+VTzusgjr@coredump.intra.peff.net> (raw)
In-Reply-To: <372227AB-E4CF-42B6-9B08-261037F39B49@gmail.com>
On Mon, Jul 26, 2021 at 11:05:27PM -0400, Evan Miller wrote:
> The described symptoms match what I am seeing. It makes sense that
> ancient hardware would bring out the bug – triggering the server
> timeout with a long local computation.
>
> Switching to protocol 0 successfully works around the issue. This
> concludes my interest in the error. I suggest reviving a discussion of
> Jeff King's patch here:
>
> https://lore.kernel.org/git/YKU4mbq%2Fam%2FliAN4@coredump.intra.peff.net/
Yeah, everything you've described is consistent with the problem being
fixed there. Good news, then: the patch is already in Git's "master"
branch, and will be part of the next release (which should be v2.33.0).
If you can reproduce the problem at will and building from master isn't
too hard, it would be nice to know if that indeed fixes it for you.
-Peff
next prev parent reply other threads:[~2021-07-27 12:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 17:54 Exit code 255 after large clone (32-bit PowerPC) Evan Miller
2021-07-26 22:09 ` brian m. carlson
2021-07-26 22:50 ` Evan Miller
2021-07-27 0:51 ` Ævar Arnfjörð Bjarmason
2021-07-27 1:37 ` brian m. carlson
2021-07-27 2:20 ` Junio C Hamano
2021-07-27 3:05 ` Evan Miller
2021-07-27 12:44 ` Jeff King [this message]
2021-07-27 2:08 ` Evan Miller
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=YP//uBa+VTzusgjr@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=emmiller@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.