Tarantool development patches archive
 help / color / mirror / Atom feed
From: Kirill Yukhin <kyukhin@tarantool.org>
To: Alexander Turenko <alexander.turenko@tarantool.org>
Cc: tarantool-patches@freelists.org,
	Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v2 0/3] lua-yaml null/boolean fixes
Date: Wed, 6 Mar 2019 10:21:18 +0300	[thread overview]
Message-ID: <20190306072118.2byjpwmvvx3nuwkv@tarantool.org> (raw)
In-Reply-To: <20190305164058.5trbjyln2lasyzoz@tkn_work_nb>

Hello,

On 05 Mar 19:40, Alexander Turenko wrote:
> On Mon, Feb 25, 2019 at 02:27:24PM +0300, Kirill Yukhin wrote:
> > Hello,
> > 
> > On 22 Jan 05:12, Alexander Turenko wrote:
> > > https://github.com/tarantool/tarantool/issues/3476
> > > https://github.com/tarantool/tarantool/issues/3662
> > > https://github.com/tarantool/tarantool/issues/3583
> > > https://github.com/tarantool/tarantool/tree/kh/gh-3662-yaml-2.1
> > > 
> > > AKhatskevich (1):
> > >   lua-yaml: verify arguments count
> > > 
> > > Alexander Turenko (2):
> > >   lua-yaml: fix boolean/null representation in yaml
> > >   lua-yaml: treat an empty document/value as null
> > 
> > I've checked your patches (1/3 and 2/3) into 2.1 branch.
> > 
> > Could you please rebase the patchset on top of 1.10 as well?
> 
> I cherry-picked these two commits on top of fresh 1.10 and all seems to
> be okay (the commits are applied cleanly and all tests are passed).
> 
> I pushed it to https://github.com/tarantool/tarantool/commits/kh/gh-3662-yaml-1.10
> Travis-CI: https://travis-ci.org/tarantool/tarantool/builds/502095402

Strange. Anyway, I've comitted it to 1.10 as well.

--
Regards, Kirill Yukhin

      reply	other threads:[~2019-03-06  7:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22  2:12 [tarantool-patches] " Alexander Turenko
2019-01-22  2:12 ` [tarantool-patches] [PATCH v2 1/3] lua-yaml: verify arguments count Alexander Turenko
2019-01-24 21:26   ` [tarantool-patches] " Vladislav Shpilevoy
2019-02-05  3:29     ` Alexander Turenko
2019-02-05 19:36       ` Vladislav Shpilevoy
2019-02-11 13:32         ` Alexander Turenko
2019-02-15 21:28           ` Vladislav Shpilevoy
2019-01-22  2:12 ` [tarantool-patches] [PATCH v2 2/3] lua-yaml: fix boolean/null representation in yaml Alexander Turenko
2019-01-24 21:26   ` [tarantool-patches] " Vladislav Shpilevoy
2019-01-24 21:32     ` Vladislav Shpilevoy
2019-02-05  3:29     ` Alexander Turenko
2019-02-05 19:36       ` Vladislav Shpilevoy
2019-02-15 21:06         ` Vladislav Shpilevoy
2019-02-15 21:23           ` Alexander Turenko
2019-02-18 18:55         ` Alexander Turenko
2019-02-22 15:14           ` Vladislav Shpilevoy
2019-01-22  2:12 ` [tarantool-patches] [PATCH v2 3/3] lua-yaml: treat an empty document/value as null Alexander Turenko
2019-01-24 21:26   ` [tarantool-patches] " Vladislav Shpilevoy
2019-02-05  3:30     ` Alexander Turenko
2019-01-24 21:26 ` [tarantool-patches] Re: [PATCH v2 0/3] lua-yaml null/boolean fixes Vladislav Shpilevoy
2019-02-25 11:27 ` Kirill Yukhin
2019-03-05 16:40   ` Alexander Turenko
2019-03-06  7:21     ` 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=20190306072118.2byjpwmvvx3nuwkv@tarantool.org \
    --to=kyukhin@tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='[tarantool-patches] Re: [PATCH v2 0/3] lua-yaml null/boolean fixes' \
    /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