From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][scarthgap 0/3] Patch review
Date: Fri, 7 Mar 2025 13:50:09 -0800 [thread overview]
Message-ID: <cover.1741384034.git.steve@sakoman.com> (raw)
Please review this set of changes for scarthgap and have comments back by
end of day Monday, March 10
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1146
The following changes since commit 45fc7048c511c433ecc23840fe6fdd61f6366a47:
systemd: add libpcre2 as RRECOMMENDS if pcre2 is enabled (2025-03-06 06:53:50 -0800)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/scarthgap-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/scarthgap-nut
Alessio Cascone (1):
tzcode-native: Fix compiler setting from 2023d version
Priyal Doshi (1):
tzdata/tzcode-native: upgrade 2024b -> 2025a
Vijay Anusuri (1):
libtasn1: upgrade 4.19.0 -> 4.20.0
meta/recipes-extended/timezone/timezone.inc | 6 +++---
meta/recipes-extended/timezone/tzcode-native.bb | 2 +-
.../gnutls/{libtasn1_4.19.0.bb => libtasn1_4.20.0.bb} | 7 +++----
3 files changed, 7 insertions(+), 8 deletions(-)
rename meta/recipes-support/gnutls/{libtasn1_4.19.0.bb => libtasn1_4.20.0.bb} (63%)
--
2.43.0
next reply other threads:[~2025-03-07 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 21:50 Steve Sakoman [this message]
2025-03-07 21:50 ` [OE-core][scarthgap 1/3] tzdata/tzcode-native: upgrade 2024b -> 2025a Steve Sakoman
2025-03-07 21:50 ` [OE-core][scarthgap 2/3] tzcode-native: Fix compiler setting from 2023d version Steve Sakoman
2025-03-07 21:50 ` [OE-core][scarthgap 3/3] libtasn1: upgrade 4.19.0 -> 4.20.0 Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2024-05-03 13:53 [OE-core][scarthgap 0/3] Patch review 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.1741384034.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