git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Daudt <me@ikke.info>
To: Thomas Hruska <thruska@cubiclesoft.com>
Cc: git@vger.kernel.org
Subject: Re: Why is part of push origin output written to stderr?
Date: Tue, 25 Jun 2019 18:26:58 +0200	[thread overview]
Message-ID: <20190625162658.GA29877@alpha> (raw)
In-Reply-To: <b9961c7b-dd8e-e08e-99bb-60923a05ce87@cubiclesoft.com>

On Tue, Jun 25, 2019 at 08:27:20AM -0700, Thomas Hruska wrote:
> 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.

Although the name implies it's used for error output, some programs also
use stderr to output anything that is separate from the standard output
of a program.

Curl for example show progress information on stderr to not intersperse
it with the normal output of curl.

The same happens here with git. You have the regular output of git push,
but any progress update is writted to stderr.

So stderr is more treated like an additional output stream rather than
only reporting errors to stderr.

Hope this helps, Kevin

> 
> -- 
> Thomas Hruska
> CubicleSoft President
> 
> http://cubiclesoft.com/
> 

      reply	other threads:[~2019-06-25 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25 15:27 Why is part of push origin output written to stderr? Thomas Hruska
2019-06-25 16:26 ` Kevin Daudt [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190625162658.GA29877@alpha \
    --to=me@ikke.info \
    --cc=git@vger.kernel.org \
    --cc=thruska@cubiclesoft.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.
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).