From: sergos 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 0/2] Fix io.close().
Date: Wed, 13 Jul 2022 14:58:37 +0300 [thread overview]
Message-ID: <06152078-EE56-4932-88EC-FE270A5402D9@tarantool.org> (raw)
In-Reply-To: <cover.1652863494.git.skaplun@tarantool.org>
Hi!
> On 18 May 2022, at 11:58, Sergey Kaplun <skaplun@tarantool.org> wrote:
>
>
> Branch: https://github.com/tarantool/luajit/tree/skaplun/lj-735-io-close-on-closed-file-full-ci
> Issue: https://github.com/LuaJIT/LuaJIT/issues/735
> PR: https://github.com/tarantool/tarantool/pull/7148
>
> CI is read due to known issue with ubuntu_22_04.
^^^^ red?
>
> Mike Pall (2):
> Fix io.close().
> Fix io.close() error message.
>
> src/lib_io.c | 28 ++++++++++++-------
> .../lj-735-io-close-on-closed-file.test.lua | 23 +++++++++++++++
> 2 files changed, 41 insertions(+), 10 deletions(-)
> create mode 100644 test/tarantool-tests/lj-735-io-close-on-closed-file.test.lua
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-07-13 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 8:58 Sergey Kaplun via Tarantool-patches
2022-05-18 8:58 ` [Tarantool-patches] [PATCH luajit 1/2] " Sergey Kaplun via Tarantool-patches
2022-07-13 11:58 ` sergos via Tarantool-patches
2022-07-14 8:04 ` Sergey Kaplun via Tarantool-patches
2022-05-18 8:58 ` [Tarantool-patches] [PATCH luajit 2/2] Fix io.close() error message Sergey Kaplun via Tarantool-patches
2022-07-13 11:58 ` sergos via Tarantool-patches
2022-07-14 7:54 ` Sergey Kaplun via Tarantool-patches
2022-07-13 11:58 ` sergos via Tarantool-patches [this message]
2022-07-13 17:45 ` [Tarantool-patches] [PATCH luajit 0/2] Fix io.close() Sergey Kaplun via Tarantool-patches
2022-11-23 7:50 ` 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=06152078-EE56-4932-88EC-FE270A5402D9@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=sergos@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit 0/2] Fix io.close().' \
/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