Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Kaplun <skaplun@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit] Fix JIT slot overflow during up-recursion.
Date: Fri, 6 Jun 2025 15:18:54 +0300	[thread overview]
Message-ID: <708d0abf-3269-4f0f-9ba6-11e79be1c64f@tarantool.org> (raw)
In-Reply-To: <aELYRTBtCbEtqQCQ@root>

[-- Attachment #1: Type: text/plain, Size: 205 bytes --]

Thanks!

On 6/6/25 15:00, Sergey Kaplun wrote:
> Hello, Sergey!
> Thanks for the review!
> Updated the commit message as you suggested and rebased branch on the
> current tarantool/master.
LGTM
>
<snipped>

[-- Attachment #2: Type: text/html, Size: 775 bytes --]

      reply	other threads:[~2025-06-06 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05  9:41 Sergey Kaplun via Tarantool-patches
2025-06-06 10:44 ` Sergey Bronnikov via Tarantool-patches
2025-06-06 12:00   ` Sergey Kaplun via Tarantool-patches
2025-06-06 12:18     ` Sergey Bronnikov via Tarantool-patches [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=708d0abf-3269-4f0f-9ba6-11e79be1c64f@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=sergeyb@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH luajit] Fix JIT slot overflow during up-recursion.' \
    /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