Tarantool development patches archive
 help / color / mirror / Atom feed
From: Kirill Yukhin <kyukhin@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Igor Munkin <imun@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH 1/1] luajit: fix string.find recording
Date: Wed, 11 Sep 2019 21:23:07 +0300	[thread overview]
Message-ID: <20190911182307.dccm6a2cwaeb6glc@tarantool.org> (raw)
In-Reply-To: <9756499526738c87e10c8c7fb2107beb6dd60e74.1567706117.git.imun@tarantool.org>

Hello,

On 05 Sep 20:57, Igor Munkin wrote:
> Fix provided within 587532e leads to invalid end index of the string
> being matched while recording
> 
> Test related to this bug is also provided within this changeset
> 
> Relates to: LuaJIT gh-505
> Fix: tarantool gh-4476

I've checked your patch into 1.10, 2.1, 2.2 and master.

--
Regards, Kirill Yukhin

      parent reply	other threads:[~2019-09-11 18:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1567706117.git.imun@tarantool.org>
2019-09-05 17:57 ` [tarantool-patches] " Igor Munkin
2019-09-06 12:05   ` [tarantool-patches] " Sergey Ostanevich
2019-09-11 18:23   ` 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=20190911182307.dccm6a2cwaeb6glc@tarantool.org \
    --to=kyukhin@tarantool.org \
    --cc=imun@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH 1/1] luajit: fix string.find recording' \
    /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