From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Dongxiao Xu <dongxiao.xu@intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] Hob: Clear the building status if command failed
Date: Mon, 07 May 2012 11:02:35 +0100 [thread overview]
Message-ID: <1336384955.23777.72.camel@ted> (raw)
In-Reply-To: <61752e5eaa9cd19b7432dba1d7b2d61e4d961118.1336370732.git.dongxiao.xu@intel.com>
On Mon, 2012-05-07 at 14:08 +0800, Dongxiao Xu wrote:
> We may meet certain command failure during build time, for example,
> out of memory. In this case, we need to clear the "building" status.
>
> This fixes [YOCTO #2371]
>
> Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
> ---
> lib/bb/ui/crumbs/hobeventhandler.py | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-05-07 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 6:08 [PATCH 0/1][PULL][1.2.1] Hob: Fix bug 2371 Dongxiao Xu
2012-05-07 6:08 ` [PATCH 1/1] Hob: Clear the building status if command failed Dongxiao Xu
2012-05-07 10:02 ` 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=1336384955.23777.72.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=dongxiao.xu@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