{"thread":{"id":"46521","subject":"git checkout's stderr v stdout usage","startedAt":"2017-08-06T17:59:18Z","lastAt":"2020-08-18T19:27:42Z","messageCount":4,"participants":["prateekrungta","rio45","nemo54","finnjones0222"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"325657","messageId":"1502042030108-7657477.post@n2.nabble.com","threadId":"46521","inReplyTo":null,"subject":"git checkout's stderr v stdout usage","fromName":"prateekrungta","fromEmail":"prateek86400@gmail.com","sentAt":"2017-08-06T17:53:50Z","receivedAt":"2017-08-06T17:59:18Z","isPatch":false,"sender":{"key":"prateek86400@gmail.com","avatar":null},"body":"```\n  git checkout -b new_branch \n```\n\nGit does what's asked except that Git's success response (\"Switched to a new\nbranch 'new_branch'\"), goes to to stderr instead of stdout. \n\nThis feels against standard unix conventions of what to output to stderr v\nstdout. It's an extra jump that people scripting `Git` keep running into\nwhen they encounter this behaviour. For e.g. other users have complained\nabout this as far back as 2010:\nhttp://git.661346.n2.nabble.com/Bugreport-Git-responds-with-stderr-instead-of-stdout-td4959280.html\n\nI'd like to suggest changing informational messages to stdout, and erroneous\nones to stderr. May I submit a patch to change this behaviour? \n\n\n\n\n\n\n--\nView this message in context: http://git.661346.n2.nabble.com/git-checkout-s-stderr-v-stdout-usage-tp7657477.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"333622","messageId":"1511803593793-0.post@n2.nabble.com","threadId":"46521","inReplyTo":"1502042030108-7657477.post@n2.nabble.com","subject":"Re: git checkout's stderr v stdout usage","fromName":"rio45","fromEmail":"jazzchristiana@gmail.com","sentAt":"2017-11-27T17:26:33Z","receivedAt":"2017-11-27T17:35:24Z","isPatch":false,"sender":{"key":"jazzchristiana@gmail.com","avatar":null},"body":"Great succession! \nI appreciates you and good to see such a positive responses. \nYou can change your ip address of  192.168.l.254 login\n<https://192-168-1-254.tech/>   and password details at anytime. \nThank you!!\n\n\n\n--\nSent from: http://git.661346.n2.nabble.com/\n"},{"id":"333951","messageId":"1512206277879-0.post@n2.nabble.com","threadId":"46521","inReplyTo":"1502042030108-7657477.post@n2.nabble.com","subject":"Re: git checkout's stderr v stdout usage","fromName":"nemo54","fromEmail":"laurellance9789@gmail.com","sentAt":"2017-12-02T09:17:57Z","receivedAt":"2017-12-02T09:25:27Z","isPatch":false,"sender":{"key":"laurellance9789@gmail.com","avatar":null},"body":"I found this an useful post. \nThanks for sharing such a valuable details. \nI appreciates you very much. \nNow, you can check your Karnataka SSLC PUC Results 2018 at anywhere.\nCheck for more information  www.karresults.nic.in\n<https://karresultsnicin.org/>  .\n\n\n\n--\nSent from: http://git.661346.n2.nabble.com/\n"},{"id":"403965","messageId":"1597778860204-0.post@n2.nabble.com","threadId":"46521","inReplyTo":"1502042030108-7657477.post@n2.nabble.com","subject":"Re: git checkout's stderr v stdout usage","fromName":"finnjones0222","fromEmail":"finnjones0222@gmail.com","sentAt":"2020-08-18T19:27:40Z","receivedAt":"2020-08-18T19:27:42Z","isPatch":false,"sender":{"key":"finnjones0222@gmail.com","avatar":null},"body":"Canon printers are one of the essentials in every office as well as\nhouseholds. To start using your Canon product you can read all required\ninformation at * ij.start.cannon\n<https://canon-comijsetup.me/ij-start-canon/>  *. The process of setup of\nprinters is available at * canon.com/ijsetup <https://canon-comijsetup.me/> \n*. Of you are still confused about something, then quickly get in touch with\nthe experts here.\n\n\n\n\n--\nSent from: http://git.661346.n2.nabble.com/\n"}]}