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

stdout vs stderr

From
FLFlorian Lohoff <f@zz.de>
Date
Feb 15, 2016, 09:59 UTC
Message-ID
<20160215095913.GB27034@pax.zz.de>

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!
Message 1 of 1 in “stdout vs stderr”
  1. Florian LohoffFeb 15, 2016

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.