public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/31239] anp_IN locale: abbreviated month names are the same as the full month names
Date: Mon, 15 Jan 2024 23:17:14 +0000	[thread overview]
Message-ID: <bug-31239-716-VHcviYVX8F@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31239-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31239

--- Comment #1 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Mike Fabian <mfabian@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=9d2703c109791d1ff0bf1f611b0b78f1703f51eb

commit 9d2703c109791d1ff0bf1f611b0b78f1703f51eb
Author: Mike FABIAN <mfabian@redhat.com>
Date:   Mon Jan 15 23:12:48 2024 +0100

    localedata: anp_IN: Fix abbreviated month names

    Resolves: BZ # 31239

    The correct abbreviated month names were apparently given in the comment
above `abmon`.
    But the value of `abmon` was apparently just copied from the value of `mon`
and this
    mistake was hard to see because code point notation <Uxxxx> was used. After
converting
    to UTF-8 it was obvious that there was apparently a copy and paste mistake.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-01-15 23:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 14:52 [Bug localedata/31239] New: " maiku.fabian at gmail dot com
2024-01-12 14:52 ` [Bug localedata/31239] " maiku.fabian at gmail dot com
2024-01-15 23:17 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-15 23:18 ` 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-31239-716-VHcviYVX8F@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).