From: "pravin.d.s at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/14094] Update locale data to Unicode 6.3
Date: Fri, 23 May 2014 13:55:00 -0000 [thread overview]
Message-ID: <bug-14094-716-JJOi4XabR6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14094-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14094
--- Comment #5 from Pravin S <pravin.d.s at gmail dot com> ---
Yeah, Backward compatibility is must.
I will write small script to check we are not changing existing maps, so we can
be confident before commiting.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-05-23 13:55 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 21:06 [Bug localedata/14094] New: Update locale data to Unicode 6.1 jsm28 at gcc dot gnu.org
2012-05-11 7:28 ` [Bug localedata/14094] " bugdal at aerifal dot cx
2013-11-26 17:07 ` myllynen at redhat dot com
2014-02-18 10:12 ` pravin.d.s at gmail dot com
2014-05-21 12:52 ` johannes at kyriasis dot com
2014-05-21 12:52 ` allan at archlinux dot org
2014-05-23 7:56 ` [Bug localedata/14094] Update locale data to Unicode 6.3 pravin.d.s at gmail dot com
2014-05-23 12:11 ` joseph at codesourcery dot com
2014-05-23 13:55 ` pravin.d.s at gmail dot com [this message]
2014-06-10 9:43 ` pravin.d.s at gmail dot com
2014-06-10 14:40 ` carlos at redhat dot com
2014-06-11 4:25 ` pravin.d.s at gmail dot com
2014-06-19 11:28 ` pravin.d.s at gmail dot com
2014-06-21 19:15 ` [Bug localedata/14094] Update locale data to Unicode 7.0.0 pravin.d.s at gmail dot com
2014-06-25 12:08 ` fweimer at redhat dot com
2014-06-25 12:43 ` pravin.d.s at gmail dot com
2014-06-25 13:54 ` carlos at redhat dot com
2014-07-04 10:51 ` pravin.d.s at gmail dot com
2014-07-17 12:44 ` pravin.d.s at gmail dot com
2014-07-22 13:03 ` pravin.d.s at gmail dot com
2014-09-05 1:08 ` carlos at redhat dot com
2014-09-29 7:29 ` maiku.fabian at gmail dot com
2014-09-29 7:30 ` pravin.d.s at gmail dot com
2014-10-14 8:08 ` maiku.fabian at gmail dot com
2014-11-06 11:03 ` maiku.fabian at gmail dot com
2014-11-06 11:03 ` maiku.fabian at gmail dot com
2014-11-06 11:05 ` maiku.fabian at gmail dot com
2014-11-06 11:22 ` maiku.fabian at gmail dot com
2014-11-06 11:56 ` maiku.fabian at gmail dot com
2014-11-06 11:59 ` maiku.fabian at gmail dot com
2014-11-06 12:09 ` maiku.fabian at gmail dot com
2014-11-12 10:15 ` pravin.d.s at gmail dot com
2014-11-12 10:25 ` pravin.d.s at gmail dot com
2014-11-14 15:10 ` maiku.fabian at gmail dot com
2014-11-14 15:10 ` maiku.fabian at gmail dot com
2014-11-14 15:10 ` maiku.fabian at gmail dot com
2014-11-14 15:10 ` maiku.fabian at gmail dot com
2014-11-14 15:11 ` maiku.fabian at gmail dot com
2014-11-24 11:28 ` maiku.fabian at gmail dot com
2014-12-01 10:38 ` maiku.fabian at gmail dot com
2014-12-03 10:01 ` maiku.fabian at gmail dot com
2014-12-03 12:47 ` maiku.fabian at gmail dot com
2014-12-03 12:47 ` maiku.fabian at gmail dot com
2014-12-04 10:35 ` maiku.fabian at gmail dot com
2015-02-21 1:04 ` cvs-commit at gcc dot gnu.org
2015-02-21 1:05 ` aoliva at sourceware dot org
2015-02-21 20:50 ` aoliva at sourceware dot org
2016-03-22 11:19 ` egmont at gmail dot com
2016-03-22 18:33 ` vapier at gentoo dot 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-14094-716-JJOi4XabR6@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).