From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/2] Hob second build fixes
Date: Mon, 5 Sep 2011 13:30:09 +0100 [thread overview]
Message-ID: <cover.1315225427.git.paul.eggleton@linux.intel.com> (raw)
The following two patches fix problems running the second build within
a single session of the hob UI.
The patches (against Poky, but apply cleanly with -p2 against BitBake
master) are available in the git repository at:
git://git.pokylinux.org/poky-contrib paule/hob-fixes
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=paule/hob-fixes
Paul Eggleton (2):
hob: clear out temporary file list after deleting
hob: fix segfault on second build
bitbake/lib/bb/ui/crumbs/runningbuild.py | 5 +++++
bitbake/lib/bb/ui/hob.py | 3 ++-
2 files changed, 7 insertions(+), 1 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-09-05 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 12:30 Paul Eggleton [this message]
2011-09-05 12:30 ` [PATCH 1/2] hob: clear out temporary file list after deleting Paul Eggleton
2011-09-05 16:39 ` Joshua Lock
2011-09-05 12:30 ` [PATCH 2/2] hob: fix segfault on second build Paul Eggleton
2011-09-05 16:39 ` Joshua Lock
2011-09-05 19:13 ` [PATCH 0/2] Hob second build fixes Richard Purdie
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=cover.1315225427.git.paul.eggleton@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox