Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [PATCH 0/4] buildhistory analysis
Date: Sun, 08 Jan 2012 21:27:13 -0800	[thread overview]
Message-ID: <4F0A7AB1.1090306@linux.intel.com> (raw)
In-Reply-To: <cover.1325785538.git.paul.eggleton@linux.intel.com>

On 01/05/2012 09:56 AM, Paul Eggleton wrote:
> The first part of the buildhistory analysis functionality (command-line
> only at the moment). It hasn't been heavily tested "in anger" yet (I
> hope we will start to use it on the Yocto Project autobuilder fairly
> soon) but it is functional.
>
> There are also a couple of improvements to buildhistory.bbclass itself.
>
> The following changes since commit 563828bad19a242bba9ce3db461bb5807037dfdf:
>
>    multilib: Abstract class extension code into classextend.py (2012-01-05 12:36:08 +0000)
>
> are available in the git repository at:
>    git://git.openembedded.org/openembedded-core-contrib paule/buildhistory-analysis
>    http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/buildhistory-analysis
>
> Paul Eggleton (4):
>    buildhistory: add script to check for significant changes
>    classes/buildhistory: add hostname to commit message
>    classes/buildhistory: make the package version backwards error
>      non-fatal
>    classes/buildhistory: remove redundant package history checking stub
>
>   meta/classes/buildhistory.bbclass    |   16 +--
>   meta/lib/oe/buildhistory_analysis.py |  240 ++++++++++++++++++++++++++++++++++
>   scripts/buildhistory-diff            |   43 ++++++
>   3 files changed, 286 insertions(+), 13 deletions(-)
>   create mode 100644 meta/lib/oe/buildhistory_analysis.py
>   create mode 100755 scripts/buildhistory-diff
>

Merged into OE-Core

Thanks
	Sau!



      parent reply	other threads:[~2012-01-09  5:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 17:56 [PATCH 0/4] buildhistory analysis Paul Eggleton
2012-01-05 17:56 ` [PATCH 1/4] buildhistory: add script to check for significant changes Paul Eggleton
2012-01-05 17:56 ` [PATCH 2/4] classes/buildhistory: add hostname to commit message Paul Eggleton
2012-01-05 17:56 ` [PATCH 3/4] classes/buildhistory: make the package version backwards error non-fatal Paul Eggleton
2012-01-05 17:56 ` [PATCH 4/4] classes/buildhistory: remove redundant package history checking stub Paul Eggleton
2012-01-09  5:27 ` Saul Wold [this message]

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=4F0A7AB1.1090306@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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