From: Jeff King <peff@peff.net>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Randall Becker" <rsbecker@nexbridge.com>,
"Baruch Burstein" <bmburstein@gmail.com>,
"Fabian Stelzer" <fs@gigacodes.de>,
"Philip Oakley" <philipoakley@iee.email>
Subject: Re: [PATCH v2] CodingGuidelines: document which output goes to stdout vs. stderr
Date: Thu, 2 Dec 2021 18:58:45 -0500 [thread overview]
Message-ID: <YaldtR9udlozfx9Z@coredump.intra.peff.net> (raw)
In-Reply-To: <20211202223110.22062-1-sunshine@sunshineco.com>
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 <sunshine@sunshineco.com>
> ---
>
> Changes since v1[*]:
>
> * tone down the commit message (peff)
:) This looks great to me. Thanks for doing it.
-Peff
prev parent reply other threads:[~2021-12-02 23:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 5:32 [PATCH] CodingGuidelines: document which output goes to stdout vs. stderr Eric Sunshine
2021-12-01 8:33 ` Fabian Stelzer
2021-12-01 13:50 ` Eric Sunshine
2021-12-01 15:14 ` Fabian Stelzer
2021-12-01 21:35 ` Junio C Hamano
2021-12-01 21:57 ` Eric Sunshine
2021-12-01 19:42 ` Jeff King
2021-12-01 20:30 ` Eric Sunshine
2021-12-01 23:27 ` Philip Oakley
2021-12-01 23:56 ` Eric Sunshine
2021-12-02 22:31 ` [PATCH v2] " Eric Sunshine
2021-12-02 23:58 ` Jeff King [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YaldtR9udlozfx9Z@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=bmburstein@gmail.com \
--cc=fs@gigacodes.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=philipoakley@iee.email \
--cc=rsbecker@nexbridge.com \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).