From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Buildhistory fix
Date: Tue, 9 May 2017 12:38:38 +1200 [thread overview]
Message-ID: <cover.1494290288.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit 123962018251dfb1d6ca5aa5c0d02534007de3ab:
build-appliance-image: Update to master head revision (2017-05-01 08:56:43 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/buildhistory-fix1
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/buildhistory-fix1
Paul Eggleton (1):
classes/buildhistory: fix failures collecting output signatures
meta/classes/buildhistory.bbclass | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
--
2.9.3
next reply other threads:[~2017-05-09 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 0:38 Paul Eggleton [this message]
2017-05-09 0:38 ` [PATCH 1/1] classes/buildhistory: fix failures collecting output signatures Paul Eggleton
-- strict thread matches above, loose matches on Subject: below --
2012-05-04 13:36 [PATCH 0/1] Buildhistory fix Paul Eggleton
2012-05-04 17:23 ` Saul Wold
2011-12-05 18:28 [PATCH 0/1] buildhistory fix Paul Eggleton
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.1494290288.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 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.