Tarantool development patches archive
 help / color / mirror / Atom feed
From: Kirill Yukhin <kyukhin@tarantool.org>
To: Serge Petrenko <sergepetrenko@tarantool.org>
Cc: tml <tarantool-patches@dev.tarantool.org>
Subject: Re: [Tarantool-patches] [avtikhon@tarantool.org: [PATCH v1] test: flaky replication/anon.test.lua test]
Date: Fri, 25 Sep 2020 18:53:35 +0300	[thread overview]
Message-ID: <20200925155335.4hv7fdfizsngwrkp@tarantool.org> (raw)
In-Reply-To: <1a439a7e-6b7c-9392-dd5b-21b40fcea992@tarantool.org>

Hello,

On 14 сен 10:29, Serge Petrenko wrote:
> 
> 11.09.2020 09:24, Alexander V. Tikhonov пишет:
> > Hi Sergey, could you please review the following patch, thank you.
> 
> Hi, Alexander!  Thanks for the patch.
> 
> 
> I don't like the idea of restarting the default instance every now and then,
> but ok.


I've checked your patch into 2.4, 2.5 and master.

--
Regards, Kirill Yukhin

      reply	other threads:[~2020-09-25 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200911062447.GA32383@hpalx>
2020-09-14  7:29 ` Serge Petrenko
2020-09-25 15:53   ` Kirill Yukhin [this message]

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=20200925155335.4hv7fdfizsngwrkp@tarantool.org \
    --to=kyukhin@tarantool.org \
    --cc=sergepetrenko@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [avtikhon@tarantool.org: [PATCH v1] test: flaky replication/anon.test.lua test]' \
    /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