From: "vapier at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/19479] gbm_IN: new Garhwali Locale
Date: Mon, 23 May 2016 20:46:00 -0000 [thread overview]
Message-ID: <bug-19479-716-RDfkmizLay@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19479-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19479
Mike Frysinger <vapier at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WORKSFORME |---
--- Comment #3 from Mike Frysinger <vapier at sourceware dot org> ---
for locales, i don't think we need to be this strict. from time to time, i'll
roll through a random locale bug and do some research/digging myself.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-05-23 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 13:17 [Bug localedata/19479] New: Adding Garhwali Local rawatkusum801 at gmail dot com
2016-01-17 13:18 ` [Bug localedata/19479] Adding Garhwali Locale rawatkusum801 at gmail dot com
2016-01-17 19:49 ` [Bug localedata/19479] gbm_IN: new " vapier at gentoo dot org
2016-04-22 3:16 ` vapier at gentoo dot org
2016-05-23 19:30 ` fweimer at redhat dot com
2016-05-23 20:46 ` vapier at sourceware dot org [this message]
2024-01-16 18:30 ` maiku.fabian at gmail dot com
2024-01-17 16:18 ` maiku.fabian at gmail dot com
2024-01-17 16:31 ` maiku.fabian at gmail dot com
2024-01-17 16:46 ` maiku.fabian at gmail dot com
2024-01-17 16:56 ` cvs-commit at gcc dot gnu.org
2024-01-17 16:56 ` cvs-commit at gcc dot gnu.org
2024-01-17 16:58 ` 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-19479-716-RDfkmizLay@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).