From: "claude at 2xlibre dot net" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/18812] New: New locale for Kabyle Algeria (kab_DZ)
Date: Wed, 12 Aug 2015 12:37:00 -0000 [thread overview]
Message-ID: <bug-18812-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=18812
Bug ID: 18812
Summary: New locale for Kabyle Algeria (kab_DZ)
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: claude at 2xlibre dot net
CC: libc-locales at sourceware dot org
Target Milestone: ---
Created attachment 8507
--> https://sourceware.org/bugzilla/attachment.cgi?id=8507&action=edit
Kabyle locale file
Here is a new locale for the Kabyle language in Algeria.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-08-12 12:37 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 12:37 claude at 2xlibre dot net [this message]
2016-02-19 10:49 ` [Bug localedata/18812] kab_DZ: new Kabyle Algeria locale vapier at gentoo dot org
2016-06-10 23:42 ` vapier at gentoo dot org
2016-06-10 23:42 ` vapier at gentoo dot org
2016-06-11 9:59 ` claude at 2xlibre dot net
2016-06-11 14:14 ` vapier at gentoo dot org
2016-07-06 21:23 ` claude at 2xlibre dot net
2016-07-06 21:23 ` claude at 2xlibre dot net
2016-08-21 18:40 ` cjlhomeaddress at gmail dot com
2016-08-22 14:09 ` cjlhomeaddress at gmail dot com
2016-11-13 19:20 ` belkacem77 at gmail dot com
2017-06-07 14:04 ` belkacem77 at gmail dot com
2017-06-08 21:03 ` carlos at redhat dot com
2017-06-08 22:49 ` belkacem77 at gmail dot com
2017-08-31 7:53 ` claude at 2xlibre dot net
2017-08-31 11:38 ` belkacem77 at gmail dot com
2017-10-20 8:11 ` maiku.fabian at gmail dot com
2017-10-20 8:41 ` maiku.fabian at gmail dot com
2017-10-20 9:07 ` maiku.fabian at gmail dot com
2017-10-20 9:11 ` maiku.fabian at gmail dot com
2017-10-20 9:12 ` maiku.fabian at gmail dot com
2017-10-20 9:16 ` belkacem77 at gmail dot com
2017-10-20 9:21 ` belkacem77 at gmail dot com
2017-10-20 9:25 ` belkacem77 at gmail dot com
2017-10-20 9:27 ` belkacem77 at gmail dot com
2017-10-20 9:31 ` belkacem77 at gmail dot com
2017-10-20 9:36 ` maiku.fabian at gmail dot com
2017-10-20 9:40 ` maiku.fabian at gmail dot com
2017-10-20 9:42 ` belkacem77 at gmail dot com
2017-10-20 9:45 ` belkacem77 at gmail dot com
2017-10-20 9:48 ` maiku.fabian at gmail dot com
2017-10-20 9:51 ` maiku.fabian at gmail dot com
2017-10-20 9:52 ` maiku.fabian at gmail dot com
2017-10-20 10:00 ` belkacem77 at gmail dot com
2017-10-20 10:05 ` belkacem77 at gmail dot com
2017-10-20 10:13 ` maiku.fabian at gmail dot com
2017-10-20 10:23 ` belkacem77 at gmail dot com
2017-10-20 11:19 ` maiku.fabian at gmail dot com
2017-10-20 11:32 ` maiku.fabian at gmail dot com
2017-10-20 14:58 ` belkacem77 at gmail dot com
2017-10-20 16:27 ` cvs-commit at gcc dot gnu.org
2017-10-20 16:27 ` maiku.fabian at gmail dot com
2017-10-20 16:42 ` claude at 2xlibre dot net
2017-10-20 17:05 ` slimane.amiri at gmail dot com
2017-10-24 8:44 ` belkacem77 at gmail dot com
2017-10-25 5:24 ` belkacem77 at gmail dot com
2017-10-25 12:16 ` maiku.fabian at gmail dot com
2017-11-02 3:05 ` cjlhomeaddress at gmail dot com
2017-11-02 6:19 ` belkacem77 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-18812-716@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).