From: Florian Lohoff <f@zz.de>
To: git@vger.kernel.org
Subject: stdout vs stderr
Date: Mon, 15 Feb 2016 10:59:13 +0100 [thread overview]
Message-ID: <20160215095913.GB27034@pax.zz.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
Hi,
is there a reason why those messages for pull are sent to stdout and
for push are sent to stderr?
flo@p3:~$ git pull
Already up-to-date.
flo@p3:~$ git pull >/dev/null
flo@p3:~$ git push
Everything up-to-date
flo@p3:~$ git push >/dev/null
Everything up-to-date
I am regularly trying to build automatisms around git and typically i
redirect stdout to /dev/null in the hope that when something goes
wrong i see error messages on stderr. This does not work for e.g. push
for obvious reason.
Flo
--
Florian Lohoff f@zz.de
We need to self-defend - GnuPG/PGP enable your email today!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
reply other threads:[~2016-02-15 10:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160215095913.GB27034@pax.zz.de \
--to=f@zz.de \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).