From: Thomas Hruska <thruska@cubiclesoft.com>
To: git@vger.kernel.org
Subject: Why is part of push origin output written to stderr?
Date: Tue, 25 Jun 2019 08:27:20 -0700 [thread overview]
Message-ID: <b9961c7b-dd8e-e08e-99bb-60923a05ce87@cubiclesoft.com> (raw)
As seen from a basic 'git push origin master' where the last part of the
output of a successful push origin is sent to stderr instead of stdout:
To host:user/something.git
1f57f4a..1a96eab master -> master
I don't usually think of a successful push as being a fatal error but I
could be very wrong. Maybe git is trying to tell me that pushing is
actually a mistake.
--
Thomas Hruska
CubicleSoft President
http://cubiclesoft.com/
next reply other threads:[~2019-06-25 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 15:27 Thomas Hruska [this message]
2019-06-25 16:26 ` Why is part of push origin output written to stderr? Kevin Daudt
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=b9961c7b-dd8e-e08e-99bb-60923a05ce87@cubiclesoft.com \
--to=thruska@cubiclesoft.com \
--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).