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

Re: [PATCH 3/3] Use /dev/null for update hook stdin.

From
Junio C Hamano <junkio@cox.net>
Date
Dec 31, 2006, 06:03 UTC
Message-ID
<7vtzzciouh.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20061231025522.GC5530@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> writes:
Show 6 quoted lines
> Currently the update hook invoked by receive-pack has its stdin
> connected to the pushing client.  The hook shouldn't attempt to
> read from this stream, and doing so may consume data that was
> meant for receive-pack.  Instead we should give the update hook
> /dev/null as its stdin, ensuring that it always receives EOF and
> doesn't disrupt the protocol if it attempts to read any data.
Both 2 and 3 look sane, but can we have a few new tests too?
Previous: Shawn O. Pearce
Message 3 of 3 in “Redirect update hook stdout to stderr.”
  1. 2/3 Redirect update hook stdout to stderr.Shawn O. Pearce, Dec 31, 2006
  2. 3/3 Use /dev/null for update hook stdin.Shawn O. Pearce, Dec 31, 2006
  3. Junio C HamanoDec 31, 2006

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.