git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: BUG: git log dies to SIGPIPE

From
Jeff King <peff@peff.net>
Date
Aug 2, 2021, 18:08 UTC
Message-ID
<YQg0t2bzqwBJ02yL@coredump.intra.peff.net>
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:
Show 9 quoted lines
> 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
Previous: Joseph JenneNext: Joseph Jenne
Message 2 of 5 in “BUG: git log dies to SIGPIPE”
  1. Joseph JenneAug 2, 2021
  2. Jeff KingAug 2, 2021
  3. Joseph JenneAug 2, 2021
  4. ZheNing HuSep 26, 2021
  5. Ævar Arnfjörð BjarmasonSep 27, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.