Re: [RFC_PATCHv4 4/7] submodule init: redirect stdout to stderr
- From
Sebastian Schuberth <sschuberth@gmail.com>
- Date
- Mar 22, 2016, 07:46 UTC
- Message-ID
- <CAHGBnuMs4D0LeMvdcS0yzKoQgmE+UTb+QFfOkSy7T20PbH86UQ@mail.gmail.com>
- In-Reply-To
- <1458612372-10966-5-git-send-email-sbeller@google.com>
On Tue, Mar 22, 2016 at 3:06 AM, Stefan Beller <sbeller@google.com> wrote:
> Reroute the output of stdout to stderr as it is just informative > messages, not to be consumed by machines.
Just wondering, what's Git's policy on this? This message is neither an error nor a warning, but just purely informational. As such it semantically does not belong to stderr, or? On the other hand I see multiple places in Git's code where printing to stderr is (mis-)used for informational messages, probably to separate output to be consumed by humans from output to be consumed by machines, like you do here.
-- Sebastian Schuberth