From: Konstantin Osipov <kostja@tarantool.org>
To: Stanislav Zudin <szudin@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v6] Feature request for a new collation
Date: Thu, 11 Apr 2019 19:42:15 +0300 [thread overview]
Message-ID: <20190411164215.GA19455@chai> (raw)
In-Reply-To: <20190411152649.3167-1-szudin@tarantool.org>
* Stanislav Zudin <szudin@tarantool.org> [19/04/11 18:28]:
> This patch contains new tests for collations.
> Those tests who is not compatible with the old ICU
> versions (prior to 60.2) are marked as "unstable".
> These tests are being skipped.
> The patch also removes a duplicate test
>
> Closes #4007
Thank you for new tests. Why skip the unstable tests? If it breaks
current builds, please add a new ticket to enable skipped tests
and remove the broken builds.
--
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov
next prev parent reply other threads:[~2019-04-11 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 15:26 [tarantool-patches] " Stanislav Zudin
2019-04-11 16:42 ` Konstantin Osipov [this message]
2019-04-12 18:32 ` [tarantool-patches] " Stanislav Zudin
2019-05-09 8:57 ` Kirill Yukhin
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=20190411164215.GA19455@chai \
--to=kostja@tarantool.org \
--cc=szudin@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH v6] Feature request for a new collation' \
/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