From: Carlos O'Donell <carlos@redhat.com>
To: Chris Leonard <cjlhomeaddress@gmail.com>,
Marko Myllynen <myllynen@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH 1/3] localedata: use same comment_char/escape_char in these files
Date: Mon, 14 Mar 2016 18:06:00 -0000 [thread overview]
Message-ID: <56E6FD96.8030508@redhat.com> (raw)
In-Reply-To: <CAHdAata8SwOO4a1QFdG3m1L6238j3eX8zscYqkPtVW6dWiLz=A@mail.gmail.com>
On 03/13/2016 01:49 PM, Chris Leonard wrote:
> I'm here because I work with glibc-dependent language communities, so
> that has been my focus. I have not tried to work with CLDR on
> locales. Anyone here have experience with that? How
> welcoming/responsive are they to people who are trying to act as
> intermediaries for minority language communities?
I don't know.
Though I'd like Red Hat to find out.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2016-03-14 18:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 7:54 Mike Frysinger
2016-02-20 7:54 ` [PATCH 2/3] localedata: standardize first few lines Mike Frysinger
2016-02-20 7:55 ` [PATCH 3/3] localedata: standardize copyright/license information [BZ #11213] Mike Frysinger
2016-02-25 20:13 ` [PATCH 1/3] localedata: use same comment_char/escape_char in these files Mike Frysinger
2016-03-09 22:24 ` Mike Frysinger
2016-03-11 10:31 ` Marko Myllynen
2016-03-11 14:24 ` Chris Leonard
2016-03-12 12:19 ` Marko Myllynen
2016-03-12 19:10 ` Chris Leonard
2016-03-13 17:50 ` Chris Leonard
2016-03-14 18:06 ` Carlos O'Donell [this message]
2016-04-11 18:58 ` Mike Frysinger
2016-04-11 20:46 ` Chris Leonard
2016-04-12 2:11 ` Mike Frysinger
2016-04-12 2:50 ` Chris Leonard
2016-03-14 18:20 ` Carlos O'Donell
2016-03-14 19:43 ` keld
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=56E6FD96.8030508@redhat.com \
--to=carlos@redhat.com \
--cc=cjlhomeaddress@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=myllynen@redhat.com \
/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).