From: "Paul Eggleton" <paul.eggleton@linux.microsoft.com>
To: openembedded-core@lists.openembedded.org
Subject: [RFC PATCH 0/2] buildhistory: record SRC_URI
Date: Sun, 18 Oct 2020 21:03:55 -0700 [thread overview]
Message-ID: <cover.1603080016.git.paul.eggleton@linux.microsoft.com> (raw)
Record SRC_URI for all built recipes in buildhistory. Since we also
want this recorded for native recipes, enable writing out the "latest"
file under packages/ for native recipes as well.
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 1f26495884b8f567aecadc5936651846dfeed3f5:
siteinfo: Recognize bigendian sh3be and sh4be (2020-10-17 23:22:15 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/buildhistory-src-uri
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/buildhistory-src-uri
Paul Eggleton (2):
classes/buildhistory: record SRC_URI
classes/buildhistory: also save recipe info for native recipes
meta/classes/buildhistory.bbclass | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-10-19 4:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 4:03 Paul Eggleton [this message]
2020-10-19 4:03 ` [RFC PATCH 1/2] classes/buildhistory: record SRC_URI 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 ` [OE-core] [RFC PATCH 0/2] buildhistory: record SRC_URI 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.1603080016.git.paul.eggleton@linux.microsoft.com \
--to=paul.eggleton@linux.microsoft.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