From: Darren Hart <dvhart@linux.intel.com>
To: Juro Bystricky <juro.bystricky@intel.com>,
<openembedded-core@lists.openembedded.org>
Cc: richard.purdie@intel.com
Subject: Re: [PATCH] oe-git-proxy: Redirect error messages to STDERR
Date: Fri, 27 Mar 2015 13:37:17 -0700 [thread overview]
Message-ID: <D13B0D59.C4118%dvhart@linux.intel.com> (raw)
In-Reply-To: <1427476655-5162-1-git-send-email-juro.bystricky@intel.com>
On 3/27/15, 10:17 AM, "Juro Bystricky" <juro.bystricky@intel.com> wrote:
>oe-git-proxy script needs socat. If socat is not found,
>an error message is issued on STDOUT. This leads to a misleading
>git message:
>
>fatal: protocol error: bad line length character: ERRO
>
>instead of the intended message:
>
>ERROR: socat binary not in PATH
>
>Redirecting the error message to STDERR fixes this issue.
>
>Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Thanks Juro, good fix.
Reviewed-by: Darren Hart <dvhart@linux.intel.com>
--
Darren Hart
Intel Open Source Technology Center
next parent reply other threads:[~2015-03-27 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1427476655-5162-1-git-send-email-juro.bystricky@intel.com>
2015-03-27 20:37 ` Darren Hart [this message]
2015-03-27 20:49 ` [PATCH] oe-git-proxy: Redirect error messages to STDERR Burton, Ross
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=D13B0D59.C4118%dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=juro.bystricky@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@intel.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