public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/30412] d_t_fmt in id_ID uses %r placeholder but am_pm and t_fmt_ampm are undefined
Date: Mon, 18 Dec 2023 09:25:26 +0000 [thread overview]
Message-ID: <bug-30412-131-OekJoJL33r@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30412-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30412
--- Comment #6 from Mike FABIAN <maiku.fabian at gmail dot com> ---
(In reply to Zhafran Rama Azmi from comment #4)
> Created attachment 15262 [details]
> attachment-3741274-0.html
>
> Hey, I would like to inform that i'm currently having this on hold, got
> one thing wrong, that is it turns out first weekday is indeed sunday
> here, so I'm going to correct that, rest are still correct. I would
> also like to collect evidence and the likes
Oh, sorry, I didn't see that before committing.
So I need to correct the first weekday to Sunday?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-12-18 9:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 10:49 [Bug localedata/30412] New: " bugzilla at tecnocode dot co.uk
2023-05-02 11:18 ` [Bug localedata/30412] " schwab@linux-m68k.org
2023-05-02 12:05 ` p3732 at getgoogleoff dot me
2023-05-15 14:33 ` bugzilla at tecnocode dot co.uk
2023-12-18 8:11 ` maiku.fabian at gmail dot com
2023-12-18 8:22 ` maiku.fabian at gmail dot com
2023-12-18 8:44 ` rushing27alien at gmail dot com
2023-12-18 9:23 ` cvs-commit at gcc dot gnu.org
2023-12-18 9:25 ` maiku.fabian at gmail dot com [this message]
2023-12-19 7:00 ` rushing27alien at gmail dot com
2023-12-19 10:23 ` cvs-commit at gcc dot gnu.org
2023-12-19 10:24 ` 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-30412-131-OekJoJL33r@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).