From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/7] buildhistory fixes
Date: Fri, 17 Feb 2012 11:36:37 +0000 [thread overview]
Message-ID: <1460092.NheOtE1WDM@helios> (raw)
In-Reply-To: <cover.1329226672.git.paul.eggleton@linux.intel.com>
On Tuesday 14 February 2012 13:40:10 Paul Eggleton wrote:
> Analysis of the recent output from buildhistory on the Yocto Project and
> Angstrom autobuilders showed a few anomalies and annoyances; this
> set of patches addresses all of the ones I noticed.
I've got one more patch to add to this, please ignore this set as v2 is on its
way.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-02-17 11:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 13:40 [PATCH 0/7] buildhistory fixes Paul Eggleton
2012-02-14 13:40 ` [PATCH 1/7] classes/buildhistory: squash spaces out of image variables Paul Eggleton
2012-02-14 13:40 ` [PATCH 2/7] classes/buildhistory: sort and de-dupe dependency graphs Paul Eggleton
2012-02-14 13:40 ` [PATCH 3/7] classes/buildhistory: sort FILELIST in package info Paul Eggleton
2012-02-14 13:40 ` [PATCH 4/7] classes/buildhistory: use hostname instead of reading /etc/hostname Paul Eggleton
2012-02-14 14:28 ` Koen Kooi
2012-02-14 13:40 ` [PATCH 5/7] classes/buildhistory: fix splitting on + in package list fields Paul Eggleton
2012-02-14 13:40 ` [PATCH 6/7] buildhistory_analysis: avoid noise due to reordering Paul Eggleton
2012-02-14 13:40 ` [PATCH 7/7] buildhistory_analysis: correctly split RDEPENDS/RRECOMMENDS Paul Eggleton
2012-02-17 11:36 ` Paul Eggleton [this message]
2012-02-21 14:57 ` [PATCH 0/7] buildhistory fixes Paul Eggleton
2012-02-21 18:45 ` Saul Wold
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=1460092.NheOtE1WDM@helios \
--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