From: prateekrungta <prateek86400@gmail.com>
To: git@vger.kernel.org
Subject: git checkout's stderr v stdout usage
Date: Sun, 6 Aug 2017 10:53:50 -0700 (MST) [thread overview]
Message-ID: <1502042030108-7657477.post@n2.nabble.com> (raw)
```
git checkout -b new_branch
```
Git does what's asked except that Git's success response ("Switched to a new
branch 'new_branch'"), goes to to stderr instead of stdout.
This feels against standard unix conventions of what to output to stderr v
stdout. It's an extra jump that people scripting `Git` keep running into
when they encounter this behaviour. For e.g. other users have complained
about this as far back as 2010:
http://git.661346.n2.nabble.com/Bugreport-Git-responds-with-stderr-instead-of-stdout-td4959280.html
I'd like to suggest changing informational messages to stdout, and erroneous
ones to stderr. May I submit a patch to change this behaviour?
--
View this message in context: http://git.661346.n2.nabble.com/git-checkout-s-stderr-v-stdout-usage-tp7657477.html
Sent from the git mailing list archive at Nabble.com.
next reply other threads:[~2017-08-06 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 17:53 prateekrungta [this message]
2017-11-27 17:26 ` git checkout's stderr v stdout usage rio45
2017-12-02 9:17 ` nemo54
2020-08-18 19:27 ` finnjones0222
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1502042030108-7657477.post@n2.nabble.com \
--to=prateek86400@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).