From: "digitalfreak at lingonborough dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/10496] 12h time representation in multiple locales faulty
Date: Fri, 28 Dec 2018 21:22:00 -0000 [thread overview]
Message-ID: <bug-10496-716-HjvLWLCOEw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10496-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=10496
Rafal Luzynski <digitalfreak at lingonborough dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |2.29
--- Comment #5 from Rafal Luzynski <digitalfreak at lingonborough dot com> ---
Fixed by the commits:
*
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=27841a7d5abe36c48b41b33d39ca8e5e14b9d36f
(Albanian);
*
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=989182c40a54c3022ff75c3c313479231dd36602
(all other locales).
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-12-28 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10496-716@http.sourceware.org/bugzilla/>
2014-07-01 9:36 ` [Bug localedata/10496] time representation in Arabian locales faulty? fweimer at redhat dot com
2014-07-01 9:38 ` nils at redhat dot com
2014-07-01 9:38 ` nils at redhat dot com
2014-07-01 21:36 ` fweimer at redhat dot com
2014-07-02 7:55 ` pravin.d.s at gmail dot com
2018-09-27 10:03 ` [Bug localedata/10496] 12h time representation in multiple locales faulty digitalfreak at lingonborough dot com
2018-12-28 21:18 ` cvs-commit at gcc dot gnu.org
2018-12-28 21:22 ` digitalfreak at lingonborough dot com [this message]
2019-01-31 17:18 ` cvs-commit at gcc dot gnu.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-10496-716-HjvLWLCOEw@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).