From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/3] Minor sstate-related fixes
Date: Tue, 15 Mar 2011 13:21:36 +0000 [thread overview]
Message-ID: <1300195296.30423.1698.camel@rex> (raw)
In-Reply-To: <cover.1298903625.git.paul.eggleton@linux.intel.com>
On Mon, 2011-02-28 at 14:37 +0000, Paul Eggleton wrote:
> From: Paul Eggleton <paul.eggleton@linux.intel.com>
>
> These patches fix two potential sources of problems with sstate stamp file
> handling and one error message issue for setscene tasks. They are not urgent
> for the 1.0 release but may be desirable.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: paule/sstate-fixes
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=paule/sstate-fixes
>
> Thanks,
> Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
>
>
> Paul Eggleton (3):
> sstate.bbclass: avoid deleting unrelated stamp files
> sstate.bbclass: always delete stamp files in sstate_clean
> bitbake/runqueue: show correct task name for setscene task failure
>
> bitbake/lib/bb/runqueue.py | 14 +++++++++++---
> meta/classes/sstate.bbclass | 20 ++++++++++----------
> 2 files changed, 21 insertions(+), 13 deletions(-)
I've merged these patches, thanks!
Richard
prev parent reply other threads:[~2011-03-15 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 14:37 [PATCH 0/3] Minor sstate-related fixes Paul Eggleton
2011-02-28 14:38 ` [PATCH 1/3] sstate.bbclass: avoid deleting unrelated stamp files Paul Eggleton
2011-02-28 14:38 ` [PATCH 2/3] sstate.bbclass: always delete stamp files in sstate_clean Paul Eggleton
2011-02-28 14:38 ` [PATCH 3/3] bitbake/runqueue: show correct task name for setscene task failure Paul Eggleton
2011-03-15 13:21 ` 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=1300195296.30423.1698.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=paul.eggleton@linux.intel.com \
--cc=poky@yoctoproject.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.