public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24162] ja_JP LC_TIME: era offset for Taisho GanNen and BC direction
Date: Wed, 06 Feb 2019 04:29:00 -0000	[thread overview]
Message-ID: <bug-24162-716-FMhzFqwvGy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24162-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24162

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tamuki at linet dot gr.jp

--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to junji morimitsu from comment #3)
> Hi ,
> 
> (In reply to Carlos O'Donell from comment #2)
> > The bug-glibc-locales@gnu.org address is in the process of being fixed, but
> 
> Thank you.  So the address will be available again, I cancel the item 1:.
> 
> 
> About 2: and 3:, I think they are simple typos.  Is there anyone who can
> confirm the fixes?
> 
> Thank you very much.  
> I'm testing Japanese era data because the new era name will be announce on
> April 1.  (logged as Bug#22964)

TAMUKI-san,

Given that you are looking at the Japanese era name change in detail, do you
have any comments on the correctness of the existing data?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2019-02-06  4:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 10:15 [Bug localedata/24162] New: " junji.morimitsu at hpe dot com
2019-02-04 10:17 ` [Bug localedata/24162] " junji.morimitsu at hpe dot com
2019-02-04 14:47 ` carlos at redhat dot com
2019-02-04 15:25 ` carlos at redhat dot com
2019-02-05 14:09 ` junji.morimitsu at hpe dot com
2019-02-06  4:29 ` carlos at redhat dot com [this message]
2019-02-07  6:17 ` tamuki at linet dot gr.jp
2019-02-07 13:04 ` junji.morimitsu at hpe dot com
2019-02-08  8:49 ` tamuki at linet dot gr.jp
2019-03-02 12:04 ` cvs-commit at gcc dot gnu.org
2019-03-18  5:53 ` tamuki at linet dot gr.jp
2019-03-22  2:01 ` cvs-commit at gcc dot gnu.org
2024-01-09 17:15 ` maiku.fabian at gmail dot com
2024-01-11 14:20 ` maiku.fabian at gmail 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-24162-716-FMhzFqwvGy@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).