From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org, "n.pettik" <korablev@tarantool.org>
Cc: "N. Tatunov" <hollow653@gmail.com>
Subject: [tarantool-patches] Re: [PATCH] sql: assertion fail on nested select
Date: Thu, 19 Jul 2018 18:22:11 +0300 [thread overview]
Message-ID: <f2a1e66c-432b-113c-1752-89fae69491d1@tarantool.org> (raw)
In-Reply-To: <C1FB7FFF-5994-4582-8D1B-2FD7AD677331@tarantool.org>
LGTM as well.
On 19/07/2018 16:09, n.pettik wrote:
> Now LGTM.
>
next prev parent reply other threads:[~2018-07-19 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 12:11 [tarantool-patches] " N.Tatunov
2018-07-17 13:59 ` [tarantool-patches] " Alexander Turenko
2018-07-18 12:34 ` Nikita Tatunov
2018-07-18 13:41 ` Nikita Tatunov
[not found] ` <07E4F387-E976-432B-A80B-E01B40BCF126@corp.mail.ru>
2018-07-18 15:37 ` Nikita Tatunov
2018-07-18 16:51 ` Alexander Turenko
2018-07-18 20:36 ` n.pettik
2018-07-19 12:47 ` Nikita Tatunov
2018-07-19 13:09 ` n.pettik
2018-07-19 15:22 ` Vladislav Shpilevoy [this message]
2018-07-20 13:21 ` 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=f2a1e66c-432b-113c-1752-89fae69491d1@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=hollow653@gmail.com \
--cc=korablev@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH] sql: assertion fail on nested select' \
/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