From: "Steve Sakoman" <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/3] Patch review
Date: Thu, 20 May 2021 14:19:26 -1000 [thread overview]
Message-ID: <cover.1621520845.git.steve@sakoman.com> (raw)
Please review this final set of patches for the 3.1.8 release and have
comments back by end of day Friday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2172
The following changes since commit cc49591d84d241d90e3dccb3e174ddfd737de311:
meta/lib/oe/rootfs.py: Fix typo "Restoreing" -> "Restoring" (2021-05-14 07:16:38 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut
Richard Purdie (2):
Revert "cml1.bbclass: Return sorted list of cfg files"
sstate: Handle manifest 'corruption' issue
Stefan Ghinea (1):
boost: fix do_fetch failure
meta/classes/cml1.bbclass | 2 +-
meta/classes/sstate.bbclass | 16 +++++++++++++++-
meta/recipes-support/boost/boost-1.72.0.inc | 2 +-
3 files changed, 17 insertions(+), 3 deletions(-)
--
2.25.1
next reply other threads:[~2021-05-21 0:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 0:19 Steve Sakoman [this message]
2021-05-21 0:19 ` [OE-core][dunfell 1/3] Revert "cml1.bbclass: Return sorted list of cfg files" Steve Sakoman
2021-05-21 0:19 ` [OE-core][dunfell 2/3] boost: fix do_fetch failure Steve Sakoman
2021-05-21 0:19 ` [OE-core][dunfell 3/3] sstate: Handle manifest 'corruption' issue Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2021-07-20 21:57 [OE-core][dunfell 0/3] Patch review Steve Sakoman
2021-11-04 14:06 Steve Sakoman
2022-03-08 14:13 Steve Sakoman
2022-03-10 14:04 Steve Sakoman
2022-07-13 19:46 Steve Sakoman
2022-09-29 2:05 Steve Sakoman
2024-01-03 3:13 Steve Sakoman
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.1621520845.git.steve@sakoman.com \
--to=steve@sakoman.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