From: Peter Seebach <peter.seebach@windriver.com>
To: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: v5 [PATCH 0/2] variable history and file inclusion tracking
Date: Mon, 8 Oct 2012 13:50:49 -0500 [thread overview]
Message-ID: <cover.1349721987.git.peter.seebach@windriver.com> (raw)
This fixes one straight up bug (wrong kind of empty container literal)
and improves clarity of messages in a number of cases by reporting who
called finalize when a finalize() operation applies overrides. Fully
supporting that for oe-core would require a couple of tweaks in oe-core,
but this improves output regardless.
The following changes since commit 90fd57ee3cb2856c10bda1f5af4879d2b7cf2668:
Cristiana Voicu (1):
hob/imageconfigurationpage: a 'hob-image' appears listed in the base image combo box
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/incvar
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/incvar
Peter Seebach (2):
data_smart.py and friends: Track file inclusions for bitbake -e
data_smart.py and friends: Track variable history
lib/bb/cooker.py | 15 ++-
lib/bb/data.py | 34 +++++-
lib/bb/data.pyc | Bin 0 -> 14383 bytes
lib/bb/data_smart.py | 235 ++++++++++++++++++++++++++++++++----
lib/bb/data_smart.pyc | Bin 0 -> 21279 bytes
lib/bb/parse/__init__.py | 3 +-
lib/bb/parse/ast.py | 25 +++-
lib/bb/parse/parse_py/BBHandler.py | 6 +-
8 files changed, 281 insertions(+), 37 deletions(-)
create mode 100644 lib/bb/data.pyc
create mode 100644 lib/bb/data_smart.pyc
next reply other threads:[~2012-10-08 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 18:50 Peter Seebach [this message]
2012-10-08 18:50 ` [PATCH 1/2] data_smart.py and friends: Track file inclusions for bitbake -e Peter Seebach
2012-10-08 18:50 ` [PATCH 2/2] data_smart.py and friends: Track variable history Peter Seebach
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.1349721987.git.peter.seebach@windriver.com \
--to=peter.seebach@windriver.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