From: Jeff King <peff@peff.net>
To: Joseph Jenne <joseph.jenne15@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: BUG: git log dies to SIGPIPE
Date: Mon, 2 Aug 2021 14:08:55 -0400 [thread overview]
Message-ID: <YQg0t2bzqwBJ02yL@coredump.intra.peff.net> (raw)
In-Reply-To: <CAB5AetcMK6=yZh4OY-0A6x6vs7X+0_1APfp4cCP_MSK_TO46ow@mail.gmail.com>
On Mon, Aug 02, 2021 at 10:46:53AM -0700, Joseph Jenne wrote:
> What did you do before the bug happened? (Steps to reproduce your issue)
> used `git log`, exiting the viewer (`less`) before reading the entire
> commit history of the project
> What did you expect to happen? (Expected behavior)
> normal exit with status code 0
> What happened instead? (Actual behavior)
> git log dies to SIGPIPE after `less` exits
> What's different between what you expected and what actually happened?
> git does not exit normally as would be expected
FWIW, there was a discussion about this a few months ago:
https://lore.kernel.org/git/YAG%2FvzctP4JwSp5x@zira.vinc17.org/
-Peff
next prev parent reply other threads:[~2021-08-02 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 17:46 BUG: git log dies to SIGPIPE Joseph Jenne
2021-08-02 18:08 ` Jeff King [this message]
2021-08-02 18:16 ` Joseph Jenne
2021-09-26 13:17 ` ZheNing Hu
2021-09-27 0:29 ` Ævar Arnfjörð Bjarmason
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=YQg0t2bzqwBJ02yL@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=joseph.jenne15@gmail.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.