From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/23996] Dutch salutations
Date: Wed, 17 Jul 2019 10:07:00 -0000 [thread overview]
Message-ID: <bug-23996-716-KQh24KW3Yq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23996-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23996
--- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Rafal Luzynski <rl@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=fba6d4bbce716b8256cb33f06ec8ae607a4556ef
commit fba6d4bbce716b8256cb33f06ec8ae607a4556ef
Author: Rafal Luzynski <digitalfreak@lingonborough.com>
Date: Tue Jul 9 11:53:43 2019 +0200
nl_BE locale: Use "copy "nl_NL"" in LC_NAME (bug 23996).
The content of the section is identical in both languages.
[BZ #23996]
* localedata/locales/nl_BE (LC_NAME): Replace with “copy "nl_NL"”.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-07-17 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 20:09 [Bug localedata/23996] New: " pander at users dot sourceforge.net
2018-12-20 9:52 ` [Bug localedata/23996] " pander at users dot sourceforge.net
2018-12-20 9:53 ` pander at users dot sourceforge.net
2018-12-31 18:21 ` digitalfreak at lingonborough dot com
2019-01-01 11:42 ` pander at users dot sourceforge.net
2019-01-01 11:53 ` pander at users dot sourceforge.net
2019-07-10 9:55 ` digitalfreak at lingonborough dot com
2019-07-10 9:58 ` pander at users dot sourceforge.net
2019-07-17 10:07 ` cvs-commit at gcc dot gnu.org
2019-07-17 10:07 ` cvs-commit at gcc dot gnu.org [this message]
2019-07-17 10:14 ` digitalfreak at lingonborough 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-23996-716-KQh24KW3Yq@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).