From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/20209] Spelling mistake for Sunday in Greenlandic kl_GL
Date: Sat, 13 Oct 2018 10:03:00 -0000 [thread overview]
Message-ID: <bug-20209-716-8ctUCt1Xe5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20209-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20209
--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, aaribaud/2.28/master has been deleted
was 5473739a7b44f27965b70d1acf480f5f72603e78
- Log -----------------------------------------------------------------
5473739a7b44f27965b70d1acf480f5f72603e78 kl_GL: Fix spelling of Sunday, should
be "sapaat" (bug 20209).
-----------------------------------------------------------------------
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-10-13 10:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-20209-716@http.sourceware.org/bugzilla/>
2017-12-04 23:48 ` [Bug localedata/20209] spelling mistake for sunday " digitalfreak at lingonborough dot com
2018-10-02 21:57 ` digitalfreak at lingonborough dot com
2018-10-02 21:58 ` cvs-commit at gcc dot gnu.org
2018-10-08 22:49 ` [Bug localedata/20209] Spelling mistake for Sunday " digitalfreak at lingonborough dot com
2018-10-08 22:57 ` cvs-commit at gcc dot gnu.org
2018-10-13 10:03 ` cvs-commit at gcc dot gnu.org [this message]
2018-10-26 15:51 ` cvs-commit at gcc dot gnu.org
2019-01-31 17:19 ` 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-20209-716-8ctUCt1Xe5@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).