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

Re: [PATCH] CodingGuidelines: document which output goes to stdout vs. stderr

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 1, 2021, 21:35 UTC
Message-ID
<xmqqtufsypmu.fsf@gitster.g>
In-Reply-To
<CAPig+cRFqO5wcZTPrpTuiBP72+6enJs+---mjT2AFAQq5ztt_w@mail.gmail.com>
Eric Sunshine <sunshine@sunshineco.com> writes:
Show 6 quoted lines
> However, I can certainly change these to say "Git command" if you
> think it would make the intent clearer, and can update the final point
> to say:
>
>     Error messages from Git commands should always
>     be sent to the stderr stream.

In an earlier round, I think there was a version without "should" in there, but I am sure we have bugs that do not follow the guideline. The proposed phrasing sounds good to me.

Thanks.
Previous: Fabian StelzerNext: Eric Sunshine
Message 5 of 12 in “CodingGuidelines: document which output goes to stdout vs. stderr”
  1. CodingGuidelines: document which output goes to stdout vs. stderrEric Sunshine, Dec 1, 2021
  2. Fabian StelzerDec 1, 2021
  3. Eric SunshineDec 1, 2021
  4. Fabian StelzerDec 1, 2021
  5. Junio C HamanoDec 1, 2021
  6. Eric SunshineDec 1, 2021
  7. Jeff KingDec 1, 2021
  8. Eric SunshineDec 1, 2021
  9. Philip OakleyDec 1, 2021
  10. Eric SunshineDec 1, 2021
  11. CodingGuidelines: document which output goes to stdout vs. stderrEric Sunshine, Dec 2, 2021
  12. Jeff KingDec 2, 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.