From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Maxim Kokryashkin <m.kokryashkin@tarantool.org>
Cc: Maxim Kokryashkin <max.kokryashkin@gmail.com>,
tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit 2/2] Fix frame for more types of on-trace error messages.
Date: Thu, 7 Sep 2023 13:06:33 +0300 [thread overview]
Message-ID: <7578c729-5fcc-694a-ca5b-085fdf08caa2@tarantool.org> (raw)
In-Reply-To: <1694077016.965578384@f528.i.mail.ru>
On 9/7/23 11:56, Maxim Kokryashkin wrote:
> Hi! Did you test it with GC64 enabled?
Seems it was a build wo enabled GC64. So LGTM.
<snipped>
next prev parent reply other threads:[~2023-09-07 10:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 10:39 [Tarantool-patches] [PATCH luajit 0/2] Fix frames for on trace errors Maxim Kokryashkin via Tarantool-patches
2023-09-05 10:39 ` [Tarantool-patches] [PATCH luajit 1/2] Fix frame for on-trace out-of-memory error Maxim Kokryashkin via Tarantool-patches
2023-09-07 8:07 ` Sergey Bronnikov via Tarantool-patches
2023-09-08 13:18 ` Maxim Kokryashkin via Tarantool-patches
2023-09-12 9:53 ` Sergey Bronnikov via Tarantool-patches
2023-09-11 8:04 ` Sergey Kaplun via Tarantool-patches
2023-09-11 11:52 ` Maxim Kokryashkin via Tarantool-patches
2023-09-05 10:39 ` [Tarantool-patches] [PATCH luajit 2/2] Fix frame for more types of on-trace error messages Maxim Kokryashkin via Tarantool-patches
2023-09-07 8:11 ` Sergey Bronnikov via Tarantool-patches
2023-09-07 8:56 ` Maxim Kokryashkin via Tarantool-patches
2023-09-07 10:06 ` Sergey Bronnikov via Tarantool-patches [this message]
2023-09-11 8:20 ` Sergey Kaplun via Tarantool-patches
2023-09-11 13:45 ` Maxim Kokryashkin via Tarantool-patches
2023-09-27 12:33 ` [Tarantool-patches] [PATCH luajit 0/2] Fix frames for on trace errors Igor Munkin via Tarantool-patches
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=7578c729-5fcc-694a-ca5b-085fdf08caa2@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=m.kokryashkin@tarantool.org \
--cc=max.kokryashkin@gmail.com \
--cc=sergeyb@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit 2/2] Fix frame for more types of on-trace error messages.' \
/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