From: Konstantin Osipov <kostja@tarantool.org>
To: tarantool-patches@freelists.org
Cc: vdavydov.dev@gmail.com, alexander.turenko@tarantool.org,
Serge Petrenko <sergepetrenko@tarantool.org>
Subject: Re: [tarantool-patches] Re: [PATCH] Extend range of printable unicode characters
Date: Thu, 18 Jul 2019 12:49:54 +0300 [thread overview]
Message-ID: <20190718094954.GC21191@atlas> (raw)
In-Reply-To: <20190718045025.wt373bnoflygqc3j@tarantool.org>
* Kirill Yukhin <kyukhin@tarantool.org> [19/07/18 09:16]:
> Hello,
>
> On 16 Jul 16:43, Serge Petrenko wrote:
> > Before the patch IS_PRINTABLE macros was used
> > to determine if given character is printable or not.
> > This macros did not take into account characters
> > encoded with 4 bytes.
> > After the patch IS_PRINTABLE is replaced with new
> > corresponding function. Now the range of printable
> > characters is: (libyaml old range) U (icu range). This
> > new range include characters encoded with 4 bytes.
> >
> > Related to tarantool/tarantool#4090
> > ---
> > https://github.com/tarantool/libyaml/tree/tarantool-gh-4090-fix
> > https://github.com/tarantool/tarantool/issues/4090
>
> New parsers are out of scope 2.2 release series, so I've checked
> your patch into master.
>
> Serge, please don't forget to upstream the patch.
Well, how does this ticket meet 2.2 release criteria? It's not a
big deal, but why did you choose to not push the bug out of the
release instead?
Working on wrong things boils down to not working on the right things.
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2019-07-18 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 13:43 Serge Petrenko
2019-07-16 18:31 ` [tarantool-patches] " Konstantin Osipov
2019-07-17 9:00 ` Serge Petrenko
2019-07-18 4:50 ` Kirill Yukhin
2019-07-18 9:49 ` Konstantin Osipov [this message]
2019-07-18 11:16 ` [tarantool-patches] " Kirill Yukhin
2019-07-18 11:38 ` Konstantin Osipov
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=20190718094954.GC21191@atlas \
--to=kostja@tarantool.org \
--cc=alexander.turenko@tarantool.org \
--cc=sergepetrenko@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=vdavydov.dev@gmail.com \
--subject='Re: [tarantool-patches] Re: [PATCH] Extend range of printable unicode characters' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox