public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "pravin.d.s at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/17475] New Bhilodi and Tulu locales
Date: Tue, 21 Jul 2015 05:20:00 -0000	[thread overview]
Message-ID: <bug-17475-716-DFhhf3tK6n@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17475-716@http.sourceware.org/bugzilla/>

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

--- Comment #15 from Pravin S <pravin.d.s at gmail dot com> ---
(In reply to Khem Raj from comment #13)
> Does this build for you ?
> I am getting 
> 
> LC_ADDRESS: field `lang_ab' must not be defined
> 
> when compiling both these locales.

Please try latest git and let me know if any problem.

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

  parent reply	other threads:[~2015-07-21  5:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10  8:45 [Bug localedata/17475] New: " t.udalova at samsung dot com
2014-10-10 12:36 ` [Bug localedata/17475] " pravin.d.s at gmail dot com
2014-10-10 12:37 ` pravin.d.s at gmail dot com
2014-10-10 12:37 ` t.udalova at samsung dot com
2014-10-13  7:34 ` t.udalova at samsung dot com
2014-11-12 11:49 ` cvs-commit at gcc dot gnu.org
2014-11-12 12:01 ` siddhesh at redhat dot com
2015-02-06 15:52 ` cvs-commit at gcc dot gnu.org
2015-03-05  8:30 ` maiku.fabian at gmail dot com
2015-03-05 11:57 ` pravin.d.s at gmail dot com
2015-06-17 12:43 ` pravin.d.s at gmail dot com
2015-07-15 10:52 ` siddhesh at redhat dot com
2015-07-15 10:52 ` cvs-commit at gcc dot gnu.org
2015-07-18  1:13 ` raj.khem at gmail dot com
2015-07-21  3:01 ` cvs-commit at gcc dot gnu.org
2015-07-21  5:20 ` pravin.d.s at gmail dot com [this message]
2015-08-05  7:33 ` 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-17475-716-DFhhf3tK6n@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).