From: Vladimir Davydov <vdavydov.dev@gmail.com>
To: Imeev Mergen <imeevma@tarantool.org>
Cc: tarantool-patches@freelists.org,
Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Subject: Re: [tarantool-patches] Re: [PATCH v2 1/2] box: create bigrefs for tuples
Date: Sat, 9 Jun 2018 14:31:02 +0300 [thread overview]
Message-ID: <20180609113102.abgyq4a2bljfdr7w@esperanza> (raw)
In-Reply-To: <8ab5a569-a85d-5c3e-68ef-5c392727ac09@tarantool.org>
Mergen,
Please resend the final version of your patch set so that I can comment
on it.
On Fri, Jun 08, 2018 at 03:03:19PM +0300, Vladislav Shpilevoy wrote:
> I have force pushed my minor fixes on the branch.
> Now the patch LGTM.
>
> Vova, please, review the patchset.
next prev parent reply other threads:[~2018-06-09 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1528388742.git.imeevma@gmail.com>
2018-06-07 16:28 ` [tarantool-patches] " imeevma
2018-06-07 21:24 ` [tarantool-patches] " Vladislav Shpilevoy
2018-06-08 10:46 ` Imeev Mergen
2018-06-08 12:03 ` Vladislav Shpilevoy
2018-06-09 11:31 ` Vladimir Davydov [this message]
2018-06-07 16:34 ` [tarantool-patches] [PATCH v2 2/2] tuple: introduce bigref hints imeevma
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=20180609113102.abgyq4a2bljfdr7w@esperanza \
--to=vdavydov.dev@gmail.com \
--cc=imeevma@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [tarantool-patches] Re: [PATCH v2 1/2] box: create bigrefs for tuples' \
/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