From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] system: generate and set C.UTF-8 locale by default
Date: Tue, 26 Jul 2022 23:41:35 +0200 [thread overview]
Message-ID: <20220726234135.3a89b278@windsurf> (raw)
In-Reply-To: <20220517192439.1034654-1-james.hilliard1@gmail.com>
Hello James,
On Tue, 17 May 2022 13:24:39 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> Now that glibc/localedef supports the C.UTF-8 locale we should default
> to it as software like systemd generally expects it to be the locale
> used.
>
> This should in general reduce the amount of locale related
> compatibility issues and is what many distros have been using for
> their default locale for quite a few years so it should be a well
> tested configuration.
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> system/Config.in | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Based on the feedback you have received, it appears that this patch
needs to be revisited to make sure it makes sense and works not just
for glibc, but also for uclibc and musl. Could you have a look at this?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-07-26 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 19:24 [Buildroot] [PATCH 1/1] system: generate and set C.UTF-8 locale by default James Hilliard
2022-05-18 18:27 ` Arnout Vandecappelle
2022-05-18 23:15 ` James Hilliard
2022-07-26 21:41 ` Thomas Petazzoni via buildroot [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=20220726234135.3a89b278@windsurf \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.