From: "tiagosilva at hush dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/15264] yesstr/nostr LC_MESSAGES lacking in many locales
Date: Sat, 08 Nov 2014 00:10:00 -0000 [thread overview]
Message-ID: <bug-15264-716-s1j5uXLmpl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15264-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15264
Tiago Silva <tiagosilva at hush dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tiagosilva at hush dot com
--- Comment #3 from Tiago Silva <tiagosilva at hush dot com> ---
Created attachment 7914
--> https://sourceware.org/bugzilla/attachment.cgi?id=7914&action=edit
Patch to correct pt_* locales
I'm sending a patch to correct all the Portuguese (pt_BR, pt_PT) locales.
The format is the same that Carlos provided in es_ES.
Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-11-08 0:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 11:42 [Bug localedata/15264] New: " daxim at cpan dot org
2013-04-06 21:07 ` [Bug localedata/15264] " carlos at redhat dot com
2013-05-03 3:28 ` carlos at redhat dot com
2014-06-13 19:14 ` fweimer at redhat dot com
2014-11-08 0:10 ` tiagosilva at hush dot com [this message]
2016-04-15 21:27 ` [Bug localedata/15264] LC_MESSAGES.yesexpr/noexpr: " vapier at gentoo dot org
2016-04-19 4:51 ` [Bug localedata/15264] LC_MESSAGES.yesstr/nostr: " vapier at gentoo dot org
2016-04-23 8:08 ` vapier at gentoo dot org
2016-04-23 8:08 ` cvs-commit at gcc dot gnu.org
2016-04-23 8:09 ` vapier at gentoo dot org
2016-08-02 3:29 ` 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-15264-716-s1j5uXLmpl@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).