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

Re: weird fatal on push when post-receive hook exists but is empty

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Apr 21, 2010, 09:28 UTC
Message-ID
<4BCEC532.5040807@viscovery.net>
In-Reply-To
<4BCEBB50.7020003@drmicha.warpmail.net>
Am 4/21/2010 10:46, schrieb Michael J Gruber:
> What are we doing differently?

Your box has a different scheduler. I doesn't run (or exit) the script soon enough that the parent (receive-pack) can get SIGPIPE when it writes refs to the script's stdin.

-- Hannes
Previous: Michael J Gruber
Message 3 of 3 in “weird fatal on push when post-receive hook exists but is empty”
  1. Sitaram ChamartyApr 20, 2010
  2. Michael J GruberApr 21, 2010
  3. Johannes SixtApr 21, 2010

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.