git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Why is part of push origin output written to stderr?

From
Kevin Daudt <me@ikke.info>
Date
Jun 25, 2019, 16:26 UTC
Message-ID
<20190625162658.GA29877@alpha>
In-Reply-To
<b9961c7b-dd8e-e08e-99bb-60923a05ce87@cubiclesoft.com>
On Tue, Jun 25, 2019 at 08:27:20AM -0700, Thomas Hruska wrote:
Show 9 quoted lines
> 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
Show 7 quoted lines
> 
> -- 
> Thomas Hruska
> CubicleSoft President
> 
> http://cubiclesoft.com/
>
Previous: Thomas Hruska
Message 2 of 2 in “Why is part of push origin output written to stderr?”
  1. Thomas HruskaJun 25, 2019
  2. Kevin DaudtJun 25, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.