From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/4] BitBake memory-resident mode fixes
Date: Fri, 9 Jun 2017 15:34:42 +0200 [thread overview]
Message-ID: <cover.1497014984.git.paul.eggleton@linux.intel.com> (raw)
Three fixes for memres and one optimisation that I noticed while working
on these.
The following changes since commit 705ab252e631903e6d2e46202b419a9e8adcd861:
bitbake-layers: check layer dependencies before adding (2017-06-05 13:33:14 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/bb-memres-fixes
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bb-memres-fixes
Paul Eggleton (4):
cookerdata: fix variable history not showing in bitbake -e with memres
cooker: fix file changes not triggering task re-execution with memres
cooker: set config valid flags in initConfigurationData()
cooker: add BB_CMDLINE to enable access to UI command line with memres
lib/bb/command.py | 3 ++-
lib/bb/cooker.py | 29 +++++++++++++++++++++--------
lib/bb/cookerdata.py | 4 ++--
3 files changed, 25 insertions(+), 11 deletions(-)
--
2.9.4
next reply other threads:[~2017-06-09 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 13:34 Paul Eggleton [this message]
2017-06-09 13:34 ` [PATCH 1/4] cookerdata: fix variable history not showing in bitbake -e with memres Paul Eggleton
2017-06-09 13:34 ` [PATCH 2/4] cooker: fix file changes not triggering task re-execution " Paul Eggleton
2017-06-09 13:34 ` [PATCH 3/4] cooker: set config valid flags in initConfigurationData() Paul Eggleton
2017-06-09 13:34 ` [PATCH 4/4] cooker: add BB_CMDLINE to enable access to UI command line with memres 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.1497014984.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 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.