From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/21217] localedata: Update months from CLDR-31
Date: Tue, 27 Jun 2017 21:32:00 -0000 [thread overview]
Message-ID: <bug-21217-716-5wtQeP0TD3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21217-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21217
--- Comment #22 from Mike FABIAN <maiku.fabian at gmail dot com> ---
I (In reply to Zack Weinberg from comment #19)
> I'm inclined to say that all patches that simply update glibc to match CLDR
> should be pre-approved. The glibc reviewers mostly don't have the knowledge
> required to assess these at all, CLDR's team does, and it's silly to leave
> these sorts of fixes hanging for months for lack of anyone who feels
> empowered to say "yes."
Yes, I think the same as Zack, we should not let this stuff hanging for
a long time, we should trust CLDR. There are some bugs in CLDR, but
we should report them as bugs against CLDR if we find any. And then let
the fix come back to glibc by syncing.
I checked Rafal’s patches in this bug as carefully as I could, I could
not find any problems. Therefore, I have committed them.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-06-27 21:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 1:54 [Bug localedata/21217] New: " digitalfreak at lingonborough dot com
2017-03-04 5:04 ` [Bug localedata/21217] " digitalfreak at lingonborough dot com
2017-03-07 23:59 ` digitalfreak at lingonborough dot com
2017-03-07 23:59 ` digitalfreak at lingonborough dot com
2017-03-08 12:23 ` piotrdrag at gmail dot com
2017-03-09 11:43 ` digitalfreak at lingonborough dot com
2017-03-09 11:43 ` digitalfreak at lingonborough dot com
2017-03-09 11:43 ` digitalfreak at lingonborough dot com
2017-03-09 11:44 ` digitalfreak at lingonborough dot com
2017-03-09 11:44 ` digitalfreak at lingonborough dot com
2017-03-09 15:43 ` ihrachys at redhat dot com
2017-03-10 23:15 ` digitalfreak at lingonborough dot com
2017-04-12 8:15 ` pravin.d.s at gmail dot com
2017-04-14 0:26 ` digitalfreak at lingonborough dot com
2017-04-18 10:32 ` amsharma at redhat dot com
2017-04-20 12:33 ` jinca at pucp dot pe
2017-05-05 11:01 ` gpopac at gmail dot com
2017-05-09 23:38 ` digitalfreak at lingonborough dot com
2017-05-16 23:09 ` gpopac at gmail dot com
2017-05-17 2:23 ` ihar.hrachyshka at gmail dot com
2017-06-10 6:44 ` f.t.public at gmail dot com
2017-06-11 23:11 ` zackw at panix dot com
2017-06-13 10:14 ` digitalfreak at lingonborough dot com
2017-06-27 21:32 ` maiku.fabian at gmail dot com [this message]
2017-06-27 21:32 ` maiku.fabian at gmail dot com
2017-06-27 21:32 ` cvs-commit at gcc dot gnu.org
2017-07-03 8:04 ` cvs-commit at gcc dot gnu.org
2017-07-06 14:23 ` cvs-commit at gcc dot gnu.org
2017-07-11 20:49 ` [Bug localedata/21217] " digitalfreak at lingonborough dot com
2017-07-26 17:02 ` cvs-commit at gcc dot gnu.org
2017-08-02 14:08 ` cvs-commit at gcc dot gnu.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-21217-716-5wtQeP0TD3@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).