From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/4] Minor improvements to error messages
Date: Thu, 12 Jan 2012 15:45:33 +0000 [thread overview]
Message-ID: <8672969.hHGhlV3Ib1@helios> (raw)
In-Reply-To: <cover.1326306561.git.paul.eggleton@linux.intel.com>
On Wednesday 11 January 2012 18:30:47 Paul Eggleton wrote:
> A few minor improvements to error output. I'm still working on some
> deeper improvements but these are ready to go in immediately.
Spoke a little too soon, I'd prefer to merge one of these patches into another
I've been working on so please ignore this series.
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-01-12 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 18:30 [PATCH 0/4] Minor improvements to error messages Paul Eggleton
2012-01-11 18:30 ` [PATCH 1/4] bitbake/knotty: don't count errors as warnings Paul Eggleton
2012-01-11 18:30 ` [PATCH 2/4] bitbake: improve error formatting for fetcher errors Paul Eggleton
2012-01-11 18:30 ` [PATCH 3/4] bitbake: make warning for initial fetch failure one line Paul Eggleton
2012-01-11 18:30 ` [PATCH 4/4] bitbake/runqueue: avoid "failed" in task summary if nothing did Paul Eggleton
2012-01-12 15:45 ` Paul Eggleton [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=8672969.hHGhlV3Ib1@helios \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.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 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.