public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] ckb_IQ, or_IN locales: Add missing reorder-end keywords
Date: Fri,  8 May 2020 08:53:09 +0000 (GMT)	[thread overview]
Message-ID: <20200508085309.75383385C426@sourceware.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1180 bytes --]

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=3404def00a1b332080fa51044733f6ead0eae5f3

commit 3404def00a1b332080fa51044733f6ead0eae5f3
Author: Florian Weimer <fweimer@redhat.com>
Date:   Fri May 8 10:51:32 2020 +0200

    ckb_IQ, or_IN locales: Add missing reorder-end keywords
    
    This suppresses a non-fatal error during locale building.
    
    Reviewed-by: Rafał Lużyński <digitalfreak@lingonborough.com>

Diff:
---
 localedata/locales/ckb_IQ | 2 ++
 localedata/locales/or_IN  | 2 ++
 2 files changed, 4 insertions(+)

diff --git a/localedata/locales/ckb_IQ b/localedata/locales/ckb_IQ
index 238c381edf..ef2f3fcf2d 100644
--- a/localedata/locales/ckb_IQ
+++ b/localedata/locales/ckb_IQ
@@ -84,6 +84,8 @@ reorder-after <S0646> % ن
 <S0648> % و
 <S06C6> % ۆ
 
+reorder-end
+
 END LC_COLLATE
 
 LC_MONETARY
diff --git a/localedata/locales/or_IN b/localedata/locales/or_IN
index 8c521512dc..cd6c78385b 100644
--- a/localedata/locales/or_IN
+++ b/localedata/locales/or_IN
@@ -116,6 +116,8 @@ reorder-after <S0B39> % ORIYA LETTER HA
 % &ଯ<<ୟ
 <U0B5F> <S0B2F>;"<BASE><VRNT1>";<MIN>;<U0B5F> % ORIYA LETTER YYA
 
+reorder-end
+
 END LC_COLLATE
 
 %%%%%%%%%%%%%


                 reply	other threads:[~2020-05-08  8:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200508085309.75383385C426@sourceware.org \
    --to=fw@sourceware.org \
    --cc=glibc-cvs@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).