From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/1] Fix for bitbake.lock handling
Date: Fri, 31 Jul 2015 10:16:32 +0100 [thread overview]
Message-ID: <cover.1438334127.git.paul.eggleton@linux.intel.com> (raw)
A patch from Richard and myself to try to fix bitbake.lock handling
properly this time.
The following changes since commit bef724057f1ea81571dd3ac5a9cf862f818434b5:
build: Exit scripts with result of last shell function (2015-07-27 16:29:11 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/bitbake-lock-fix
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bitbake-lock-fix
Richard Purdie (1):
cooker: properly fix bitbake.lock handling
lib/bb/command.py | 6 ------
lib/bb/cooker.py | 30 ++++++++++++++++++++++++++++++
lib/bb/main.py | 1 +
lib/bb/tinfoil.py | 1 +
lib/bb/ui/knotty.py | 20 --------------------
lib/bb/utils.py | 29 +++++++++++++++++++++++++----
6 files changed, 57 insertions(+), 30 deletions(-)
--
2.1.0
next reply other threads:[~2015-07-31 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 9:16 Paul Eggleton [this message]
2015-07-31 9:16 ` [PATCH 1/1] cooker: properly fix bitbake.lock handling Paul Eggleton
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.1438334127.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