From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/2] fetch2: make fetch failure errors more readable
Date: Mon, 24 Sep 2012 12:14:31 +0100 [thread overview]
Message-ID: <1348485271.8662.6.camel@ted> (raw)
In-Reply-To: <1348419936-13985-1-git-send-email-paul.eggleton@linux.intel.com>
On Sun, 2012-09-23 at 18:05 +0100, Paul Eggleton wrote:
> Most of the time we don't need to see the fetch command; the fetch log
> includes the command as a debug message in any case, so omit it. Also
> adjust the way command output is printed (we don't need stderr/stdout
> labelled, and print "no output" instead of "output:\nNone" when there is
> no output.
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
> bitbake/lib/bb/fetch2/__init__.py | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-09-24 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 17:05 [PATCH 1/2] fetch2: make fetch failure errors more readable Paul Eggleton
2012-09-23 17:05 ` [PATCH 2/2] fetch2: improve error output for checksum failures Paul Eggleton
2012-09-24 11:14 ` Richard Purdie [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=1348485271.8662.6.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.