From: Jonathan Nieder <jrnieder@gmail.com>
To: Michael Hunley <michael@codecobblers.com>
Cc: git@vger.kernel.org
Subject: Re: stdout versus stderr for cmd line git
Date: Thu, 9 May 2013 20:28:43 -0700 [thread overview]
Message-ID: <20130510032843.GA12036@elie> (raw)
In-Reply-To: <CAKk5qjVoDUzeurgAL51jixXsm4rJCMCDf620vAv_Gsafk8N7iA@mail.gmail.com>
Hi,
Michael Hunley wrote:
> Ok, we can filter that out. But worse is that actual errors in a pull
> request are sent to stdout instead of standard error. For example,
> merge conflicts or pull failures because you have unstaged changes.
Yes, errors and progress output should go to stderr. The git-pull.sh
script is pretty old and is probably just a bit sloppy about
forgetting to redirect output from "echo". Patches welcome.
(See Documentation/SubmittingPatches for details.)
Hope that helps,
Jonathan
prev parent reply other threads:[~2013-05-10 3:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 1:48 stdout versus stderr for cmd line git Michael Hunley
2013-05-10 3:28 ` Jonathan Nieder [this message]
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=20130510032843.GA12036@elie \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=michael@codecobblers.com \
/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).