From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/4] Developer workflow related enhancements / fixes
Date: Mon, 8 Dec 2014 10:50:21 +0000 [thread overview]
Message-ID: <cover.1418034514.git.paul.eggleton@linux.intel.com> (raw)
The following series is the set of BitBake changes that are part of the
developer workflow improvements currently being worked on [1].
Of particular note is the final patch for resetting the class handlers
object - this was discovered incidentally and fixes a rather nasty bug.
It should probably be considered separately from the rest of the series.
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=6662
The following changes since commit 94d9590a4310f96396e8e782bcf65918f4dcdb36:
bitbake: Update to 1.25.0 as development version after release (2014-12-03 12:14:43 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/devtool-bb
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/devtool-bb
Paul Eggleton (4):
utils: add exec_flat_python_func()
fetch2: add means of disabling SRC_URI checksums
event: add a means of filtering events internally
event: fix resetting class handlers object
lib/bb/event.py | 9 +++++++++
lib/bb/fetch2/__init__.py | 3 ++-
lib/bb/utils.py | 22 ++++++++++++++++++++++
3 files changed, 33 insertions(+), 1 deletion(-)
--
1.9.3
next reply other threads:[~2014-12-08 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 10:50 Paul Eggleton [this message]
2014-12-08 10:50 ` [PATCH 1/4] utils: add exec_flat_python_func() Paul Eggleton
2014-12-08 10:50 ` [PATCH 2/4] fetch2: add means of disabling SRC_URI checksums Paul Eggleton
2014-12-08 10:50 ` [PATCH 3/4] event: add a means of filtering events internally Paul Eggleton
2014-12-08 10:50 ` [PATCH 4/4] event: fix resetting class handlers object Paul Eggleton
2014-12-08 17:42 ` Richard Purdie
2014-12-08 18:09 ` Paul Eggleton
2014-12-08 20:57 ` 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.1418034514.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.