From: "Paul Eggleton" <bluelightning@bluelightning.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [RFC PATCH 0/2] buildhistory: record SRC_URI
Date: Tue, 20 Oct 2020 10:16:17 +1300 [thread overview]
Message-ID: <2298543.jE0xQCEvom@linc> (raw)
In-Reply-To: <cover.1603080016.git.paul.eggleton@linux.microsoft.com>
On Monday, 19 October 2020 17:03:55 NZDT 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.
Hmm, this should not have been RFC. Consider this a regular patch series.
Thanks
Paul
prev parent reply other threads:[~2020-10-19 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 4:03 [RFC PATCH 0/2] buildhistory: record SRC_URI Paul Eggleton
2020-10-19 4:03 ` [RFC PATCH 1/2] classes/buildhistory: " Paul Eggleton
2020-10-26 6:43 ` [OE-core] " Mikko Rapeli
2020-10-28 14:21 ` Richard Purdie
2020-10-29 9:18 ` Mikko Rapeli
2020-10-29 11:35 ` Richard Purdie
2020-10-19 4:03 ` [RFC PATCH 2/2] classes/buildhistory: also save recipe info for native recipes Paul Eggleton
2020-10-19 21:16 ` 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=2298543.jE0xQCEvom@linc \
--to=bluelightning@bluelightning.org \
--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