{"thread":{"id":"41412","subject":"stdout vs stderr","startedAt":"2016-02-15T09:59:13Z","lastAt":"2016-02-15T09:59:13Z","messageCount":1,"participants":["Florian Lohoff"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"278149","messageId":"20160215095913.GB27034@pax.zz.de","threadId":"41412","inReplyTo":null,"subject":"stdout vs stderr","fromName":"Florian Lohoff","fromEmail":"f@zz.de","sentAt":"2016-02-15T09:59:13Z","receivedAt":"2016-02-15T09:59:13Z","isPatch":false,"sender":{"key":"f@zz.de","avatar":null},"body":"\nHi,\nis there a reason why those messages for pull are sent to stdout and\nfor push are sent to stderr?\n\nflo@p3:~$ git pull\nAlready up-to-date.\nflo@p3:~$ git pull >/dev/null\n\nflo@p3:~$ git push\nEverything up-to-date\nflo@p3:~$ git push >/dev/null\nEverything up-to-date\n\nI am regularly trying to build automatisms around git and typically i\nredirect stdout to /dev/null in the hope that when something goes\nwrong i see error messages on stderr. This does not work for e.g. push\nfor obvious reason.\n\nFlo\n-- \nFlorian Lohoff                                                 f@zz.de\n      We need to self-defend - GnuPG/PGP enable your email today!\n"}]}