From: Peter Seebach <peter.seebach@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: v2 [PATCH 0/2] data_smart.py: Track inclusions and assignments
Date: Mon, 21 May 2012 10:10:30 -0500 [thread overview]
Message-ID: <cover.1337612802.git.peter.seebach@windriver.com> (raw)
This revised patch now uses Python's traceback facility to assign
meaningful locations (file and function, rather than line) to operations
which weren't specified, and correspondingly does not specify file and
line when the file name would have been the python code making the
assignment; this makes the patch smaller and the output more meaningful.
As before, this is a patch to add tracking showing when and how variables
got their values, and which configuration files were included from which
other configuration files.
The following changes since commit 39adb5741d9eee0879d3181be505400dffc60804:
Andrei Gherzan (1):
bb/fetch2/__init__.py: Don't try to compute checksums for directories
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/tracking
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/tracking
Peter Seebach (2):
data_smart.py: Provide (optional) logging of variable modifications
data_smart.py: Track configuration file inclusions
lib/bb/cooker.py | 2 +
lib/bb/data.py | 65 +++++++++++++++++-----
lib/bb/data_smart.py | 140 +++++++++++++++++++++++++++++++++++++--------
lib/bb/parse/__init__.py | 6 ++-
lib/bb/parse/ast.py | 65 ++++++++++++----------
5 files changed, 209 insertions(+), 69 deletions(-)
next reply other threads:[~2012-05-21 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 15:10 Peter Seebach [this message]
2012-05-21 15:10 ` [PATCH 1/2] data_smart.py: Provide (optional) logging of variable modifications Peter Seebach
2012-05-21 15:10 ` [PATCH 2/2] data_smart.py: Track configuration file inclusions Peter Seebach
2012-05-21 19:54 ` v2 [PATCH 0/2] data_smart.py: Track inclusions and assignments Chris Larson
2012-05-21 20:26 ` Peter Seebach
2012-05-22 13:43 ` Richard Purdie
2012-05-22 16:13 ` Peter Seebach
2012-05-25 6:56 ` Richard Purdie
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.1337612802.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 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.