Thread (10 messages) 10 messages, 4 authors, 2021-12-02

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

From: Jeff King <hidden>
Date: 2021-12-02 23:58:48

On Thu, Dec 02, 2021 at 05:31:10PM -0500, Eric Sunshine wrote:
It has long been practice on this project for a command to emit its
primary output to stdout so that it can be captured to a file or sent
down a pipe, and to emit "chatty" messages (such as those reporting
progress) to stderr so that they don't interfere with the primary
output. However, this practice is not necessarily universal; another
common practice is to send only error messages to stderr, and all other
messages to stdout. Therefore, help newcomers out by documenting how
stdout and stderr are used on this project.

Signed-off-by: Eric Sunshine <redacted>
---

Changes since v1[*]:

* tone down the commit message (peff)
:) This looks great to me. Thanks for doing it.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help