From: Carlos O'Donell <carlos@redhat.com>
To: Mike FABIAN <mfabian@redhat.com>,
GLIBC Devel <libc-alpha@sourceware.org>
Cc: Joseph Myers <joseph@codesourcery.com>,
Pravin Satpute <psatpute@redhat.com>,
Jens Petersen <petersen@redhat.com>
Subject: Re: [PATCH v4] Update the i18n, UTF-8 and translit_* files to Unicode 9.0.0 [BZ #20313]
Date: Tue, 21 Feb 2017 13:32:00 -0000 [thread overview]
Message-ID: <debe8480-3b0b-646f-2efc-1c0160b9d80e@redhat.com> (raw)
In-Reply-To: <s9d60o6rnmi.fsf_-_@redhat.com>
On 11/02/2016 09:56 AM, Mike FABIAN wrote:
> Mike FABIAN <mfabian@redhat.com> wrote:
>
>> Joseph Myers <joseph@codesourcery.com> wrote:
>>
>>> On Wed, 29 Jun 2016, Mike FABIAN wrote:
>>>
>>>> Version 2.24
>>>> +* Unicode 9.0.0 Support: Character encoding, character type info, and
>>>
>>> There should be a blank line between the Version line and the first NEWS
>>> entry for the release.
>>
>> OK.
>>
>> New patch attached (includes the changes requested by Mike Frysinger).
>
> I rebased the patch to current master.
>
> Maybe it can be applied now?
The Unicode 9.0.0 changes have been in Fedora Rawhide for 8 months with no
adverse reported problems.
I have applied this to master.
commit 0b38d66a4e2e0d7cb9f40da5bc6e795e20cf3088
Author: Mike FABIAN <mfabian@redhat.com>
Date: Tue Feb 21 06:30:38 2017 -0500
Bug 20313: Update to Unicode 9.0.0
* Unicode 9.0.0 Support: Character encoding, character type info, and
transliteration tables are all updated to Unicode 9.0.0, using
generator scripts contributed by Mike FABIAN (Red Hat).
--
Cheers,
Carlos.
prev parent reply other threads:[~2017-02-21 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 14:57 [PATCH] Update the i18n, UTF-8 and translit_* files to Unicode 9.0.0 Mike FABIAN
2016-06-29 15:24 ` Albert ARIBAUD
2016-06-29 15:41 ` [PATCH v2] " Mike FABIAN
2016-06-29 16:18 ` Mike Frysinger
2016-06-29 17:25 ` Joseph Myers
2016-06-30 7:09 ` [PATCH v3] Update the i18n, UTF-8 and translit_* files to Unicode 9.0.0 [BZ #20313] Mike FABIAN
2016-11-02 13:58 ` [PATCH v4] " Mike FABIAN
2017-02-21 13:32 ` Carlos O'Donell [this message]
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=debe8480-3b0b-646f-2efc-1c0160b9d80e@redhat.com \
--to=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=mfabian@redhat.com \
--cc=petersen@redhat.com \
--cc=psatpute@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).