From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/22964] The Japanese Era name will be changed on May 1, 2019
Date: Wed, 03 Apr 2019 22:27:00 -0000 [thread overview]
Message-ID: <bug-22964-716-26wJfRNsOp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22964-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22964
--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, release/2.28/master has been updated
via 7423da211d1490d9fc76c2f0ce49e5dd90ea9bcc (commit)
from 4aeff335ca19286ee2382d8eba794ae5fd49281a (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=7423da211d1490d9fc76c2f0ce49e5dd90ea9bcc
commit 7423da211d1490d9fc76c2f0ce49e5dd90ea9bcc
Author: TAMUKI Shoichi <tamuki@linet.gr.jp>
Date: Wed Apr 3 18:23:14 2019 -0400
ja_JP locale: Add entry for the new Japanese era [BZ #22964]
The Japanese era name will be changed on May 1, 2019. The Japanese
government made a preliminary announcement on April 1, 2019.
The glibc ja_JP locale must be updated to include the new era name for
strftime's alternative year format support.
This is a minimal cherry pick of just the required locale changes.
(cherry picked from commit 466afec30896585b60c2106df7a722a86247c9f3)
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 6 ++++++
NEWS | 4 ++++
localedata/locales/ja_JP | 4 +++-
3 files changed, 13 insertions(+), 1 deletions(-)
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2019-04-03 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 8:09 [Bug localedata/22964] New: " fweimer at redhat dot com
2019-04-01 8:50 ` [Bug localedata/22964] " fweimer at redhat dot com
2019-04-01 8:54 ` fweimer at redhat dot com
2019-04-02 7:50 ` cvs-commit at gcc dot gnu.org
2019-04-02 18:49 ` carlos at redhat dot com
2019-04-03 4:01 ` cvs-commit at gcc dot gnu.org
2019-04-03 17:46 ` cvs-commit at gcc dot gnu.org
2019-04-03 20:35 ` srl@icu-project.org
2019-04-03 22:27 ` cvs-commit at gcc dot gnu.org [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=bug-22964-716-26wJfRNsOp@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).