{"thread":{"id":"51380","subject":"Why is part of push origin output written to stderr?","startedAt":"2019-06-25T15:37:03Z","lastAt":"2019-06-25T16:36:36Z","messageCount":2,"participants":["Thomas Hruska","Kevin Daudt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"378023","messageId":"b9961c7b-dd8e-e08e-99bb-60923a05ce87@cubiclesoft.com","threadId":"51380","inReplyTo":null,"subject":"Why is part of push origin output written to stderr?","fromName":"Thomas Hruska","fromEmail":"thruska@cubiclesoft.com","sentAt":"2019-06-25T15:27:20Z","receivedAt":"2019-06-25T15:37:03Z","isPatch":false,"sender":{"key":"thruska@cubiclesoft.com","avatar":null},"body":"As seen from a basic 'git push origin master' where the last part of the \noutput of a successful push origin is sent to stderr instead of stdout:\n\nTo host:user/something.git\n    1f57f4a..1a96eab  master -> master\n\nI don't usually think of a successful push as being a fatal error but I \ncould be very wrong.  Maybe git is trying to tell me that pushing is \nactually a mistake.\n\n-- \nThomas Hruska\nCubicleSoft President\n\nhttp://cubiclesoft.com/\n\n"},{"id":"378025","messageId":"20190625162658.GA29877@alpha","threadId":"51380","inReplyTo":"b9961c7b-dd8e-e08e-99bb-60923a05ce87@cubiclesoft.com","subject":"Re: Why is part of push origin output written to stderr?","fromName":"Kevin Daudt","fromEmail":"me@ikke.info","sentAt":"2019-06-25T16:26:58Z","receivedAt":"2019-06-25T16:36:36Z","isPatch":false,"sender":{"key":"me@ikke.info","avatar":"https://avatars.githubusercontent.com/u/135698?v=4"},"body":"On Tue, Jun 25, 2019 at 08:27:20AM -0700, Thomas Hruska wrote:\n> As seen from a basic 'git push origin master' where the last part of the\n> output of a successful push origin is sent to stderr instead of stdout:\n> \n> To host:user/something.git\n>    1f57f4a..1a96eab  master -> master\n> \n> I don't usually think of a successful push as being a fatal error but I\n> could be very wrong.  Maybe git is trying to tell me that pushing is\n> actually a mistake.\n\nAlthough the name implies it's used for error output, some programs also\nuse stderr to output anything that is separate from the standard output\nof a program.\n\nCurl for example show progress information on stderr to not intersperse\nit with the normal output of curl.\n\nThe same happens here with git. You have the regular output of git push,\nbut any progress update is writted to stderr.\n\nSo stderr is more treated like an additional output stream rather than\nonly reporting errors to stderr.\n\nHope this helps, Kevin\n\n> \n> -- \n> Thomas Hruska\n> CubicleSoft President\n> \n> http://cubiclesoft.com/\n> \n"}]}