From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 5/5] utfcpp: upgrade 4.2.0 -> 4.2.1
Date: Mon, 21 Sep 2026 15:58:35 +0100 [thread overview]
Message-ID: <20260921145835.1106731-5-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <20260921145835.1106731-1-richard.purdie@linuxfoundation.org>
3d1ff6d Release 4.2.1
32e3ed1 next16: report invalid_utf16 for a lone trail surrogate at the end of a range (#147)
30e55c2 Add utf8cpp::utf8cpp target available when consuming directly (#146)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
.../recipes-support/utfcpp/{utfcpp_4.2.0.bb => utfcpp_4.2.1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/utfcpp/{utfcpp_4.2.0.bb => utfcpp_4.2.1.bb} (94%)
diff --git a/meta/recipes-support/utfcpp/utfcpp_4.2.0.bb b/meta/recipes-support/utfcpp/utfcpp_4.2.1.bb
similarity index 94%
rename from meta/recipes-support/utfcpp/utfcpp_4.2.0.bb
rename to meta/recipes-support/utfcpp/utfcpp_4.2.1.bb
index c56d03b7c74..e891b7fc576 100644
--- a/meta/recipes-support/utfcpp/utfcpp_4.2.0.bb
+++ b/meta/recipes-support/utfcpp/utfcpp_4.2.1.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=e4224ccaecb14d942c71d31bef20d78c \
SRC_URI = "git://github.com/nemtrif/utfcpp;protocol=https;branch=master;tag=v${PV} \
file://run-ptest"
-SRCREV = "2d8e20b22dcb3e9b3c4f52103182ebda949c6089"
+SRCREV = "3d1ff6dbf54e471c846dff55dda6c8ee10c0ee5c"
inherit cmake ptest
prev parent reply other threads:[~2026-09-21 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 14:58 [PATCH 1/5] cairo: upgrade 1.18.4 -> 1.18.6 Richard Purdie
2026-09-21 14:58 ` [PATCH 2/5] harfbuzz: upgrade 14.4.0 -> 14.5.0 Richard Purdie
2026-09-21 14:58 ` [PATCH 3/5] python3-pyparsing: upgrade 3.3.2 -> 3.3.3 Richard Purdie
2026-09-21 14:58 ` [PATCH 4/5] stress-ng: upgrade 0.22.00 -> 0.22.01 Richard Purdie
2026-09-21 14:58 ` Richard Purdie [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=20260921145835.1106731-5-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.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