From: Jeff King <peff@peff.net>
To: Marat Radchenko <marat@slonopotamus.org>
Cc: git@vger.kernel.org
Subject: Re: [BUG] git push writes to stderr instead of stdout on success
Date: Mon, 19 May 2014 11:49:09 -0400 [thread overview]
Message-ID: <20140519154909.GD20289@sigill.intra.peff.net> (raw)
In-Reply-To: <20140519150358.GA3099@seldon>
On Mon, May 19, 2014 at 07:03:58PM +0400, Marat Radchenko wrote:
> `git push` writes to stderr instead of stdout
That's by design.
Which one is correct is largely a matter of philosophy / mental model.
This case has been discussed before:
http://thread.gmane.org/gmane.comp.version-control.git/180673
Keep in mind also that "git push --porcelain" does go to stdout and is
machine-parsed, so no other messages can go to stdout when that option
is enabled.
-Peff
next prev parent reply other threads:[~2014-05-19 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 15:03 [BUG] git push writes to stderr instead of stdout on success Marat Radchenko
2014-05-19 15:49 ` Jeff King [this message]
2014-05-19 16:43 ` Marat Radchenko
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=20140519154909.GD20289@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=marat@slonopotamus.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).