From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24409] Updates for TW locales
Date: Thu, 08 Apr 2021 03:12:30 +0000 [thread overview]
Message-ID: <bug-24409-716-0NalOxKI5D@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24409-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24409
--- Comment #15 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Wei-Lun Chao from comment #14)
> [PING]
> Patch-passed for version 2.33
> Please confirm.
Please review the contribution checklist for submitting patches:
https://sourceware.org/glibc/wiki/Contribution%20checklist
The most important part of a locale change is the rationale for the change from
the existing locale to the new changes.
Generally the strongest rationale is that the data is being harmonized with
CLDR from Unicode.
Your next step here would be to prepare a patch to send to
libc-alpha@sourceware.org with a commit message that is sufficiently detailed
to explain the changes. I would avoid spurious white space changes in the patch
and focus on the exact meaningful changes.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-08 3:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 10:10 [Bug localedata/24409] New: " bluebat at member dot fsf.org
2019-04-19 9:05 ` [Bug localedata/24409] " bluebat at member dot fsf.org
2019-05-10 5:23 ` bluebat at member dot fsf.org
2019-07-05 2:56 ` bluebat at member dot fsf.org
2019-08-07 2:56 ` bluebat at member dot fsf.org
2019-10-16 6:00 ` bluebat at member dot fsf.org
2019-10-24 1:28 ` [PING][PATCH]Re: " Wei-Lun Chao
2019-11-12 2:00 ` bluebat at member dot fsf.org
2019-11-25 5:22 ` bluebat at member dot fsf.org
2019-12-26 1:31 ` bluebat at member dot fsf.org
2020-02-04 5:16 ` bluebat at member dot fsf.org
2020-05-19 1:39 ` bluebat at member dot fsf.org
2020-07-08 5:39 ` bluebat at member dot fsf.org
2020-10-16 9:09 ` bluebat at member dot fsf.org
2020-10-28 2:28 ` bluebat at member dot fsf.org
2020-11-12 8:57 ` bluebat at member dot fsf.org
2021-04-08 1:48 ` bluebat at member dot fsf.org
2021-04-08 3:12 ` carlos at redhat dot com [this message]
2021-04-21 5:28 ` bluebat at member dot fsf.org
2021-11-19 14:58 ` bluebat at member dot fsf.org
2021-11-19 14:58 ` bluebat at member dot fsf.org
2021-11-26 5:00 ` bluebat at member dot fsf.org
2021-12-20 1:15 ` bluebat at member dot fsf.org
2022-01-27 7:42 ` bluebat at member dot fsf.org
2022-02-17 9:53 ` bluebat at member dot fsf.org
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=bug-24409-716-0NalOxKI5D@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).