From: Kirill Yukhin <kyukhin@tarantool.org>
To: sergeyb@tarantool.org
Cc: Sergey Bronnikov <estetus@gmail.com>,
tarantool-patches@dev.tarantool.org, v.shpilevoy@tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v7 0/3] Fix luacheck warnings in test/box-tap, test/box and test/box-py
Date: Fri, 25 Dec 2020 10:37:40 +0000 [thread overview]
Message-ID: <20201225103740.bbnb2q4hnlsov2yw@tarantool.org> (raw)
In-Reply-To: <cover.1608647958.git.estetus@gmail.com>
Hello,
On 22 Dec 17:54, Sergey Bronnikov via Tarantool-patches wrote:
> From: Sergey Bronnikov <estetus@gmail.com>
>
> Changelog v7:
> - rebased to master branch and fixed new warnings
> - splitted a huge patch series for test/ to a separate issues and patches series
> (other patches will follow)
>
> Changelog v6:
>
> - splitted patch in test/ for patches per sub-directory
> - adjusted supressions in .luacheckrc
> - fixed formatting issues in .luacheckrc
> - fixed warnings in test/vinyl/vinyl.lua and test/vinyl/large.lua
> - added commit with bumping luajit version
> - fixed warnings in test/app-tap/lua/serializer_test.lua
>
> NOTE: most luacheck patches includes changes in .luacheckrc so branch with
> patches from this patch series includes uncommitted (but with one LGTM) patches
> for test/app and test/app-tap (ligurio/gh-5453-luacheck-warnings-test-app-tap).
>
> 1. https://lists.tarantool.org/pipermail/tarantool-patches/2020-December/021385.html
>
> Gitlab CI: https://gitlab.com/tarantool/tarantool/-/pipelines/233332402
> GH branch: ligurio/gh-5455-luacheck-warnings-test-box
> GH issues:
> - https://github.com/tarantool/tarantool/issues/5455
> - https://github.com/tarantool/tarantool/issues/5456
> - https://github.com/tarantool/tarantool/issues/5457
I've checked your patchset into 2.5, 2.6 and master.
--
Regards, Kirill Yukhin
next prev parent reply other threads:[~2020-12-25 10:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 14:54 sergeyb
2020-12-22 14:54 ` [Tarantool-patches] [PATCH 1/3] luacheck: fix warnings in test/box sergeyb
2021-01-11 17:52 ` Vladislav Shpilevoy via Tarantool-patches
2021-01-12 15:26 ` Sergey Bronnikov via Tarantool-patches
2021-01-13 7:58 ` Sergey Bronnikov via Tarantool-patches
2021-01-13 16:38 ` Vladislav Shpilevoy via Tarantool-patches
2021-01-14 7:49 ` Sergey Bronnikov via Tarantool-patches
2020-12-22 14:54 ` [Tarantool-patches] [PATCH v7 2/3] luacheck: fix warnings in test/box-py sergeyb
2020-12-22 14:54 ` [Tarantool-patches] [PATCH v7 3/3] luacheck: fix warnings in test/box-tap sergeyb
2021-01-11 17:52 ` Vladislav Shpilevoy via Tarantool-patches
2021-01-12 13:59 ` Sergey Bronnikov via Tarantool-patches
2021-01-12 14:52 ` Vladislav Shpilevoy via Tarantool-patches
2021-01-12 15:21 ` Sergey Bronnikov via Tarantool-patches
2020-12-25 10:37 ` Kirill Yukhin [this message]
2020-12-30 10:17 ` [Tarantool-patches] [PATCH v7 0/3] Fix luacheck warnings in test/box-tap, test/box and test/box-py Kirill Yukhin
2020-12-30 12:27 ` Leonid Vasiliev
2021-01-14 21:34 ` Vladislav Shpilevoy via Tarantool-patches
2021-01-15 9:48 ` Kirill Yukhin 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=20201225103740.bbnb2q4hnlsov2yw@tarantool.org \
--to=kyukhin@tarantool.org \
--cc=estetus@gmail.com \
--cc=sergeyb@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v7 0/3] Fix luacheck warnings in test/box-tap, test/box and test/box-py' \
/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