public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug locale/30243] GB18030-2022 is not supported!
Date: Wed, 16 Aug 2023 19:20:02 +0000 [thread overview]
Message-ID: <bug-30243-131-CJ5WXSgbXV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30243-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30243
--- Comment #14 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Michael Matz from comment #13)
> Could this be given some attention please? AFAICS the last version of the
> patch didn't receive further suggestions, so maybe it's good to go?
> (Background:
> people here are starting to worry about gb18030-2022 conformance, and
> ideally we
> want to include/backport only something that upstream also has)
I agree completely that this needs review.
I reviewed v1, Andreas reviewed v2. The patch is currently at v3, and that
version needs review:
https://patchwork.sourceware.org/project/glibc/patch/20230627121549.3431-1-lijianglin2@huawei.com/
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-16 19:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 17:05 [Bug locale/30243] New: " starcold14 at gmail dot com
2023-03-18 17:12 ` [Bug locale/30243] " starcold14 at gmail dot com
2023-04-19 9:44 ` starcold14 at gmail dot com
2023-05-20 22:52 ` bruno at clisp dot org
2023-05-21 11:22 ` schwab@linux-m68k.org
2023-06-16 1:28 ` liqingqing3 at huawei dot com
2023-06-16 1:54 ` bruno at clisp dot org
2023-06-16 1:54 ` bruno at clisp dot org
2023-06-16 2:01 ` bruno at clisp dot org
2023-06-25 6:21 ` lijianglin2 at huawei dot com
2023-06-27 6:15 ` lijianglin2 at huawei dot com
2023-06-28 8:45 ` lijianglin2 at huawei dot com
2023-06-28 14:33 ` liqingqing3 at huawei dot com
2023-07-03 8:09 ` lijianglin2 at huawei dot com
2023-07-26 19:14 ` jamborm at gcc dot gnu.org
2023-08-16 13:26 ` matz at suse dot de
2023-08-16 19:20 ` carlos at redhat dot com [this message]
2023-08-16 19:20 ` [Bug locale/30243] Add full support for GB18030-2022 carlos at redhat dot com
2023-08-16 20:22 ` maiku.fabian at gmail dot com
2023-08-16 20:28 ` carlos at redhat dot com
2023-08-17 1:55 ` liqingqing3 at huawei dot com
2023-08-17 10:25 ` maiku.fabian at gmail dot com
2023-08-29 17:04 ` maiku.fabian at gmail dot com
2023-08-29 17:04 ` maiku.fabian at gmail dot com
2023-08-29 17:31 ` carlos at redhat dot com
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-30243-131-CJ5WXSgbXV@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).