From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 0/2] Buildhistory improvements
Date: Fri, 22 Mar 2013 19:52:39 +0000 [thread overview]
Message-ID: <1719358.HAyqquL0cm@helios> (raw)
In-Reply-To: <cover.1363981627.git.paul.eggleton@linux.intel.com>
On Friday 22 March 2013 19:47:38 Paul Eggleton wrote:
> Please review the following changes for suitability for inclusion. If you
> have any objections or suggestions for improvement, please respond to the
> patches. If you agree with the changes, please provide your Acked-by.
>
> The following changes since commit 7846f68537a942d340d5931e23a4fceb84b6edcb:
>
> vte: Fix conflict between FILES_${PN}-dbg and FILES_vte-dbg (2013-03-22
> 17:05:09 +0000)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib
> paule/buildhistory-fix5
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paul
> e/buildhistory-fix5
>
> Paul Eggleton (2):
> classes/buildhistory: implement history collection for SDKs
> classes/buildhistory: trim trailing spaces in file listings
Oops, these were not meant to be RFC. I'll repost to avoid confusion.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-03-22 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 19:47 [RFC PATCH 0/2] Buildhistory improvements Paul Eggleton
2013-03-22 19:47 ` [RFC PATCH 1/2] classes/buildhistory: implement history collection for SDKs Paul Eggleton
2013-03-22 19:47 ` [RFC PATCH 2/2] classes/buildhistory: trim trailing spaces in file listings Paul Eggleton
2013-03-22 19:52 ` Paul Eggleton [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=1719358.HAyqquL0cm@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