public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "Diego (Egor) Kobylkin" <egor@kobylkin.com>
To: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
	"libc-locales@sourceware.org" <libc-locales@sourceware.org>
Subject: Re: [PING^7][PATCH v12] Locales: Cyrillic -> ASCII transliteration [BZ #2872]
Date: Wed, 29 May 2019 14:06:00 -0000	[thread overview]
Message-ID: <RyxRHsCW6I1v9GAbQPG7zOXjWBoU5fvnU9zvehSHIit7LIXuicOn9zbkiEHd-qzgnL7ApuqWj2UfHfaaJP2J412V7wukkITUQEFaLi4Zkpc=@kobylkin.com> (raw)

Ping. Upkeeping the good tradition of pings.
Egor Kobylkin

P.S. the mailing keeps catching me refusing html vs text :-)



‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, May 10, 2019 2:19 PM, Marko Myllynen <myllynen@redhat.com> wrote:

> Hi Carlos,
>
> On 16/04/2019 22.06, Carlos O'Donell wrote:
>
> > On 4/16/19 2:41 PM, Egor Kobylkin wrote:
> >
> > > It is exactly the reason we had 12 iterations on this patch - we
> > > wanted to cover the most complete yet workable standard for the
> > > table. What we reference in the bug memo is the actual accepted
> > > standard. It is coalesced with the extended standard for further
> > > outdated cyrillic letters.
> >
> > I agree, and this is what makes review complicated and time
> > consuming. I'm relying on you as the expert, and my goal is only
> > to spot check for any inconsistencies.
>
> I know you've been very busy with everything else but did you happen to
> have any chance to check this further, shall we still wait for your
> results or how would you suggests us to proceed?
>
> Thanks,
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Marko Myllynen


                 reply	other threads:[~2019-05-29 14:06 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='RyxRHsCW6I1v9GAbQPG7zOXjWBoU5fvnU9zvehSHIit7LIXuicOn9zbkiEHd-qzgnL7ApuqWj2UfHfaaJP2J412V7wukkITUQEFaLi4Zkpc=@kobylkin.com' \
    --to=egor@kobylkin.com \
    --cc=libc-alpha@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).