From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/2] A couple more memres fixes
Date: Wed, 14 Jun 2017 12:10:23 +0200 [thread overview]
Message-ID: <cover.1497434991.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit 8d0a76f5a595dddf16b7268bae2c00ef5f568316:
ConfHandler.py: allow require or include with multiple parameters (2017-06-12 15:28:25 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/bb-memres-fixes2
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bb-memres-fixes2
Paul Eggleton (2):
cooker: fix always loading cache on every UI start with memres
cooker: ensure graceful exit after exception during BuildCompleted handler
lib/bb/cooker.py | 23 ++++++++++++++++-------
1 file changed, 16 insertions(+), 7 deletions(-)
--
2.9.4
next reply other threads:[~2017-06-14 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 10:10 Paul Eggleton [this message]
2017-06-14 10:10 ` [PATCH 1/2] cooker: fix always loading cache on every UI start with memres Paul Eggleton
2017-06-14 10:10 ` [PATCH 2/2] cooker: ensure graceful exit after exception during BuildCompleted handler 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.1497434991.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