From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] A couple of buildhistory-diff fixes
Date: Mon, 28 May 2012 13:57:10 +0100 [thread overview]
Message-ID: <cover.1338209763.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit 363424cdc78cafa278008f973c2b4288297ebf8c:
image.bbclass: Ensure ${S} is cleaned at the start of rootfs generation (2012-05-25 11:28:00 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/buildhistory-fixes6
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/buildhistory-fixes6
Paul Eggleton (2):
buildhistory_analysis: fix error when version specifier missing
scripts/buildhistory-diff: add GitPython version check
meta/lib/oe/buildhistory_analysis.py | 2 +-
scripts/buildhistory-diff | 8 ++++++--
2 files changed, 7 insertions(+), 3 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-05-28 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 12:57 Paul Eggleton [this message]
2012-05-28 12:57 ` [PATCH 1/2] buildhistory_analysis: fix error when version specifier missing Paul Eggleton
2012-05-28 12:57 ` [PATCH 2/2] scripts/buildhistory-diff: add GitPython version check Paul Eggleton
2012-05-30 12:02 ` [PATCH 0/2] A couple of buildhistory-diff fixes 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.1338209763.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