From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Tretter <m.tretter@pengutronix.de>,
Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH] migrate_ptx: add typo fix GLIBC_GCONF_BASE -> GLIBC_GCONV_BASE
Date: Thu, 3 Aug 2023 14:12:46 +0200 [thread overview]
Message-ID: <20230803121246.1768543-1-rhi@pengutronix.de> (raw)
In-Reply-To: <20230708070255.2205928-1-m.olbrich@pengutronix.de>
Fixes: a5ff1ad3a24c700884a1 (2023-07-04, "glibc: fix typo GLIBC_GCONF_BASE -> GLIBC_GCONV_BASE")
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
Would something like this make sense so it gets renamed automatically on
how ptxdist migrate"?
- Roland
scripts/migrate/migrate_ptx | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/scripts/migrate/migrate_ptx b/scripts/migrate/migrate_ptx
index 7f8c09e06a0b..9da48c38b1dd 100755
--- a/scripts/migrate/migrate_ptx
+++ b/scripts/migrate/migrate_ptx
@@ -460,3 +460,10 @@ s/^\(\(# \)\?PTXCONF_LIGHTTPD_MOD_\)COMPRESS\>/\1DEFLATE/
# reason : upstream util-linux-ng fork was renamed back to util-linux over a decade ago
#
s/^\(\(# \)\?PTXCONF_UTIL_LINUX\)_NG/\1/
+
+# from : ptxdist-2023.06.0
+# to : ptxdist-2023.07.0
+# symbol : GLIBC_GCONF_BASE -> GLIBC_GCONV_BASE
+# reason : fix typo in kconfig option
+#
+s/^\(\(# \)\?PTXCONF_GLIBC_GCONF_BASE\>/PTXCONF_GLIBC_GCONV_BASE/
--
2.39.2
next prev parent reply other threads:[~2023-08-03 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 7:18 [ptxdist] [PATCH] glibc: fix typo " Michael Tretter
2023-07-08 7:02 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-08-03 12:12 ` Roland Hieber [this message]
2023-08-03 12:18 ` [ptxdist] [PATCH v2] migrate_ptx: add typo fix " Roland Hieber
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=20230803121246.1768543-1-rhi@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=m.tretter@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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