From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] buildhistory analysis improvements
Date: Thu, 19 Jan 2012 10:32:08 +0000 [thread overview]
Message-ID: <cover.1326968802.git.paul.eggleton@linux.intel.com> (raw)
Collect and monitor some additional information about images, and
report other (possibly non-monitored) changes when a monitored item
changes to provide context.
Additionally a couple of minor issues where found in field handling for
the package info files.
The following changes since commit a0f5dd25a37fe3b8664c2133e80b6214559f93f6:
package_rpm.bbclass: Add support for filenames with spaces (2012-01-17 16:20:46 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/buildhistory-imginfo
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/buildhistory-imginfo
Paul Eggleton (4):
buildhistory: record additional image info
buildhistory_analysis: correctly handle whitespace when splitting
lists
buildhistory_analysis: improve field handling robustness
buildhistory_analysis: include related fields in output
meta/classes/buildhistory.bbclass | 18 +++++
meta/lib/oe/buildhistory_analysis.py | 127 ++++++++++++++++++++++++----------
2 files changed, 109 insertions(+), 36 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-01-19 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 10:32 Paul Eggleton [this message]
2012-01-19 10:32 ` [PATCH 1/4] buildhistory: record additional image info Paul Eggleton
2012-01-19 10:32 ` [PATCH 2/4] buildhistory_analysis: correctly handle whitespace when splitting lists Paul Eggleton
2012-01-19 10:32 ` [PATCH 3/4] buildhistory_analysis: improve field handling robustness Paul Eggleton
2012-01-19 10:32 ` [PATCH 4/4] buildhistory_analysis: include related fields in output Paul Eggleton
2012-01-19 14:33 ` [PATCH 0/4] buildhistory analysis improvements 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.1326968802.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@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