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

Re: [RFC PATCH 1/2] Report exec errors from run-command

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 25, 2009, 08:40 UTC
Message-ID
<7vd423e9as.fsf@alter.siamese.dyndns.org>
In-Reply-To
<7vr5qjecbb.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
>  - At first reading, the "while (close(fd) < 0 && errno != EBADF);"
>    pattern was a bit of eyesore.  It might be worth factoring that out to
>    a small static helper function that a smart compiler would
>    automatically inline (or mark it as a static inline).
This also is a minor style thing, but we prefer your
>>+		while(close(report_pipe[1]) < 0 && errno != EBADF);
formatted like this:
	while (foobar)
        	; /* noop */
to
 (1) have SP after syntactic keyword like while/if/switch to differentiate
     from function calls; and 
 (2) make the no-op stand out for a bit more visibility.
 
Previous: Junio C HamanoNext: Ilari Liusvaara
Message 5 of 11 in “Report remote helper exec failures”
  1. 0/2 Report remote helper exec failuresIlari Liusvaara, Dec 24, 2009
  2. 1/2 Report exec errors from run-commandIlari Liusvaara, Dec 24, 2009
  3. Junio C HamanoDec 25, 2009
  4. Junio C HamanoDec 25, 2009
  5. Junio C HamanoDec 25, 2009
  6. Ilari LiusvaaraDec 25, 2009
  7. Johannes SixtDec 25, 2009
  8. Ilari LiusvaaraDec 25, 2009
  9. 2/2 Improve transport helper exec failure reportingIlari Liusvaara, Dec 24, 2009
  10. Junio C HamanoDec 25, 2009
  11. Ilari LiusvaaraDec 25, 2009

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.