From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/5] tinfoil/other fixes for devtool/recipetool
Date: Thu, 31 Aug 2017 11:30:42 +1200 [thread overview]
Message-ID: <cover.1504135776.git.paul.eggleton@linux.intel.com> (raw)
Some changes in aid of fixing issues with OE's devtool and recipetool.
The following changes since commit 8a60106c6f7d586c793b965c5e9460b6016fab15:
main: Attempt to gain bitbake.lock rather than just waiting (2017-08-24 11:19:41 +0100)
are available in the git repository at:
git://git.openembedded.org/bitbake-contrib paule/tinfoil-fixes-bb4
http://cgit.openembedded.org/bitbake-contrib/log/?h=paule/tinfoil-fixes-bb4
Paul Eggleton (5):
tinfoil: fix log message doubling when config_only=False
tinfoil: ensure log lines get printed when tasks fail
tinfoil: ensure variable history tracking works when parsing a recipe
cooker: ensure we can run buildFileInternal() after cache is populated
fetch2/npm: add noverify parameter to skip lockdown/shrinkwrap
lib/bb/cooker.py | 8 ++++----
lib/bb/fetch2/npm.py | 41 +++++++++++++++++++++--------------------
lib/bb/tinfoil.py | 47 ++++++++++++++++++++++++++++++++++++-----------
lib/bb/ui/knotty.py | 50 +++++++++++++++++++++++++++-----------------------
4 files changed, 88 insertions(+), 58 deletions(-)
--
2.9.5
next reply other threads:[~2017-08-30 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 23:30 Paul Eggleton [this message]
2017-08-30 23:30 ` [PATCH 1/5] tinfoil: fix log message doubling when config_only=False Paul Eggleton
2017-08-30 23:30 ` [PATCH 2/5] tinfoil: ensure log lines get printed when tasks fail Paul Eggleton
2017-08-30 23:30 ` [PATCH 3/5] tinfoil: ensure variable history tracking works when parsing a recipe Paul Eggleton
2017-08-30 23:30 ` [PATCH 4/5] cooker: ensure we can run buildFileInternal() after cache is populated Paul Eggleton
2017-08-30 23:30 ` [PATCH 5/5] fetch2/npm: add noverify parameter to skip lockdown/shrinkwrap 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.1504135776.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.