From: "aurelien at aurel32 dot net" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24046] New: en_US locale doesn't define date_fmt
Date: Sun, 30 Dec 2018 23:39:00 -0000 [thread overview]
Message-ID: <bug-24046-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24046
Bug ID: 24046
Summary: en_US locale doesn't define date_fmt
Product: glibc
Version: 2.29
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: aurelien at aurel32 dot net
CC: libc-locales at sourceware dot org
Target Milestone: ---
The en_US locale default to the 12h format in t_fmt and d_t_fmt (which is
correct), but doesn't define date_fmt. This causes the date to be printed
inconsistently between the various formats:
$ date ; date +%c ; date +%X
Sun Dec 30 18:38:58 EST 2018
Sun 30 Dec 2018 06:38:58 PM EST
06:38:58 PM
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-12-30 23:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 23:39 aurelien at aurel32 dot net [this message]
2019-01-02 12:20 ` [Bug localedata/24046] " fweimer at redhat dot com
2019-01-07 13:58 ` cvs-commit at gcc dot gnu.org
2019-01-07 14:01 ` aurelien at aurel32 dot net
2019-01-31 17:17 ` cvs-commit at gcc dot gnu.org
2019-03-29 22:19 ` dilfridge at gentoo dot org
2019-03-29 22:52 ` aurelien at aurel32 dot net
2019-04-02 20:33 ` cloos at jhcloos dot com
2019-04-02 20:58 ` schwab@linux-m68k.org
2020-03-12 2:37 ` sourceware at nerdbynature dot de
2020-03-12 9:09 ` schwab@linux-m68k.org
2020-05-05 13:57 ` carlos at redhat 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-24046-716@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).