From: Florian Weimer <fw@deneb.enyo.de>
To: "Naïm Favier via Libc-stable" <libc-stable@sourceware.org>
Cc: "Naïm Favier" <n@monade.li>
Subject: Re: Backport Unicode updates?
Date: Sun, 22 Jan 2023 15:39:43 +0100 [thread overview]
Message-ID: <877cxeeiq8.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <37983ebf-6323-6dd1-de0c-0d26df2b237c@monade.li> (=?iso-8859-1?Q?=22Na=EFm?= Favier via Libc-stable"'s message of "Thu, 24 Nov 2022 11:41:28 +0100")
* Naïm Favier via Libc-stable:
> It would be nice to backport Unicode updates (and more generally
> changes to locale data, I guess) to release branches, so that
> distributions can include them more quickly. See
> https://github.com/weechat/weechat/issues/79,
> https://github.com/NixOS/nixpkgs/issues/202548 for more context.
>
> For example, could the Unicode 15 support in 7fe6734d28 be
> backported to the stable 2.36 (and maybe 2.35) branches without
> breaking anything?
Changes to collation order and case conversion have broken on-disk
data structures in the past (such as B-tree indices for PostgreSQL).
So it's not risk-free.
next prev parent reply other threads:[~2023-01-22 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 10:41 Naïm Favier
2023-01-22 14:39 ` Florian Weimer [this message]
2023-01-22 23:16 ` Carlos O'Donell
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=877cxeeiq8.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-stable@sourceware.org \
--cc=n@monade.li \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).