From: Wang Mingyu < wangmy@fujitsu.com>
To: openembedded-core@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH 04/12] ed: upgrade 1.22.2 -> 1.22.3
Date: Tue, 30 Dec 2025 17:17:05 +0800 [thread overview]
Message-ID: <20251230091714.1501-4-wangmy@fujitsu.com> (raw)
In-Reply-To: <20251230091714.1501-1-wangmy@fujitsu.com>
From: Wang Mingyu <wangmy@fujitsu.com>
Changes in version 1.22.3:
- The change to print the file name escaped when replaced into a shell command
has been reverted.
- When '--unsafe-names' is not specified, only the control characters \a, \b,
\t, \v, \f, \n, \r, \033, and \177 are now rejected in file names.
- 'make check' now checks file names with non-ASCII characters coded either in
ISO-8859-1 or in UTF-8.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
meta/recipes-extended/ed/{ed_1.22.2.bb => ed_1.22.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-extended/ed/{ed_1.22.2.bb => ed_1.22.3.bb} (93%)
diff --git a/meta/recipes-extended/ed/ed_1.22.2.bb b/meta/recipes-extended/ed/ed_1.22.3.bb
similarity index 93%
rename from meta/recipes-extended/ed/ed_1.22.2.bb
rename to meta/recipes-extended/ed/ed_1.22.3.bb
index 80d4e116ac..1a5a28a039 100644
--- a/meta/recipes-extended/ed/ed_1.22.2.bb
+++ b/meta/recipes-extended/ed/ed_1.22.3.bb
@@ -19,7 +19,7 @@ bindir = "${base_bindir}"
SRC_URI = "${GNU_MIRROR}/ed/${BP}.tar.lz"
UPSTREAM_CHECK_URI = "${GNU_MIRROR}/ed/"
-SRC_URI[sha256sum] = "f58d15242056e15af76f13f34c60d890fa2a2d5cb0abef91c115e4d83794ffe3"
+SRC_URI[sha256sum] = "47a55ddfc52d4a1ff6f7559fbd00cf948a16b6cf151ec520392761aeae4e97be"
EXTRA_OEMAKE = "-e MAKEFLAGS="
--
2.43.0
next prev parent reply other threads:[~2025-12-30 9:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 9:17 [OE-core] [PATCH 01/12] bind: upgrade 9.20.15 -> 9.20.16 Wang Mingyu
2025-12-30 9:17 ` [OE-core] [PATCH 02/12] boost: upgrade 1.89.0 -> 1.90.0 Wang Mingyu
2025-12-30 9:17 ` [OE-core] [PATCH 03/12] cups: upgrade 2.4.15 -> 2.4.16 Wang Mingyu
2025-12-30 9:17 ` Wang Mingyu [this message]
2025-12-30 9:17 ` [OE-core] [PATCH 05/12] ell: upgrade 0.80 -> 0.81 Wang Mingyu
2025-12-30 9:17 ` [OE-core] [PATCH 06/12] iso-codes: upgrade 4.18.0 -> 4.19.0 Wang Mingyu
2025-12-30 9:17 ` [OE-core] [PATCH 07/12] ninja: upgrade 1.13.1 -> 1.13.2 Wang Mingyu
2025-12-30 9:17 ` [OE-core] [PATCH 08/12] quota: upgrade 4.10 -> 4.11 Wang Mingyu
2025-12-30 9:17 ` [OE-core] [PATCH 09/12] re2c: upgrade 4.3 -> 4.3.1 Wang Mingyu
2025-12-30 9:17 ` [OE-core] [PATCH 10/12] repo: upgrade 2.59 -> 2.60.1 Wang Mingyu
2025-12-30 9:17 ` [OE-core] [PATCH 11/12] xcb-util-cursor: upgrade 0.1.5 -> 0.1.6 Wang Mingyu
2025-12-30 9:17 ` [OE-core] [PATCH 12/12] xkbcomp: upgrade 1.4.7 -> 1.5.0 Wang Mingyu
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=20251230091714.1501-4-wangmy@fujitsu.com \
--to=wangmy@fujitsu.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