From: Joseph Jenne <joseph.jenne15@gmail.com>
To: git@vger.kernel.org
Subject: BUG: git log dies to SIGPIPE
Date: Mon, 2 Aug 2021 10:46:53 -0700 [thread overview]
Message-ID: <CAB5AetcMK6=yZh4OY-0A6x6vs7X+0_1APfp4cCP_MSK_TO46ow@mail.gmail.com> (raw)
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
Anything else you want to add:
[System Info]
git version:
git version 2.30.2
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-2 (2021-07-20) x86_64
compiler info: gnuc: 10.2
libc info: glibc: 2.31
$SHELL (typically, interactive shell): /bin/zsh
next reply other threads:[~2021-08-02 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 17:46 Joseph Jenne [this message]
2021-08-02 18:08 ` BUG: git log dies to SIGPIPE Jeff King
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='CAB5AetcMK6=yZh4OY-0A6x6vs7X+0_1APfp4cCP_MSK_TO46ow@mail.gmail.com' \
--to=joseph.jenne15@gmail.com \
--cc=git@vger.kernel.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 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 NNTP newsgroup(s).