From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v3] Add new C.UTF-8 locale (Bug 17318)
Date: Thu, 18 Feb 2021 22:34:27 -0500 [thread overview]
Message-ID: <09256bae-e03c-262e-def8-a4a143c2bb19@redhat.com> (raw)
In-Reply-To: <20210219032748.564216-1-carlos@redhat.com>
On 2/18/21 10:27 PM, Carlos O'Donell wrote:
> The new locale is NOT added to SUPPORTED. Minimal test data for
> specific code points (minus those not supported by collate-test) is
> provided in C.UTF-8.in, and this verifies code point sorting is
> working reasonably across the range.
>
> The next step is to reduce LC_COLLATE to a manageable size before we
> enable the locale in SUPPORTED. Fully testing C.UTF-8 collation can
> add ~5-7 minutes to the locale testing (collate-test, and xfrm-test
> twice) so we don't enable full testing of all code points until we
> can parallelize the sort-test test. Testing sort-test with C.UTF-8
> minimal test data passes cleanly.
My apologies for the multiple posts.
I was testing why patchwork won't process this patch.
Cheers,
Carlos.
next prev parent reply other threads:[~2021-02-19 3:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 3:27 [PATCH v3] Add new C.UTF-8 locale (Bug 17318) Carlos O'Donell via Libc-alpha
2021-02-19 3:34 ` Carlos O'Donell via Libc-alpha [this message]
2021-02-19 8:47 ` Andreas Schwab
2021-03-11 19:05 ` Florian Weimer via Libc-alpha
2021-03-11 19:19 ` Florian Weimer via Libc-alpha
2021-03-11 22:55 ` Carlos O'Donell via Libc-alpha
2021-04-28 11:54 ` Carlos O'Donell via Libc-alpha
2021-04-28 17:36 ` Joseph Myers
2021-04-29 11:43 ` Carlos O'Donell via Libc-alpha
2021-04-29 11:57 ` Carlos O'Donell via Libc-alpha
-- strict thread matches above, loose matches on Subject: below --
2021-02-19 3:26 Carlos O'Donell via Libc-alpha
2021-02-19 3:22 Carlos O'Donell via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09256bae-e03c-262e-def8-a4a143c2bb19@redhat.com \
--to=libc-alpha@sourceware.org \
--cc=carlos@redhat.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 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).