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

> On 01.12.2021 00:32, Eric Sunshine wrote:
> >+ We make a distinction between a command's primary output and output
> >+ which is merely chatty feedback (for instance, status messages,
> >+ running transcript, or progress display), as well as error messages.
> >+ Roughly speaking, a command's primary output is that which one might
> >+ want to capture to a file or send down a pipe; its chatty output
> >+ should not interfere with those use-cases.
> >+
> >+ As such, primary output should be sent to the standard output stream
> >+ (stdout), and chatty output should be sent to the standard error
> >+ stream (stderr). Examples of commands which produce primary output
> >+ include `git log`, `git show`, and `git branch --list` which generate
> >+ output on the stdout stream.
> >+
> >+ Not all commands have primary output; this is often true of commands
> >+ whose main function is to perform an action. Some action commands are
> >+ silent, whereas others are chatty. An example of a chatty action
> >+ commands is `git clone` with its "Cloning into '<path>'..." and
> >+ "Checking connectivity..." status messages which it sends to the
> >+ stderr stream.
> >+
> >+ Error messages are always sent to the stderr stream.
>
> This is not necessarily true in the context of the tests.
> We just spoke about this in:
> https://lore.kernel.org/git/211130.86wnkpd6ou.gmgdl@evledraar.gmail.com/T/#u
>
> I don't think it necessary to bloat this explanation with the test details.
> But mentioning it as an exception would be good.