From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org
Cc: kostja@tarantool.org
Subject: [tarantool-patches] Re: [PATCH 0/7] swim lua preparation, again
Date: Wed, 15 May 2019 13:02:44 +0300 [thread overview]
Message-ID: <8f3025a1-257c-e810-ae18-c7fe8b8ef89d@tarantool.org> (raw)
In-Reply-To: <cover.1557875116.git.v.shpilevoy@tarantool.org>
Pushed to the master.
On 15/05/2019 02:06, Vladislav Shpilevoy wrote:
> This patchset consists of patches quite independent and needed for proper
> functioning of SWIM Lua API. Most of them are refactoring, and a couple of bug
> fixes.
>
> Branch: http://github.com/tarantool/tarantool/tree/gerold103/swim-lua-preparation
> Issue: https://github.com/tarantool/tarantool/issues/3234
>
> Vladislav Shpilevoy (7):
> swim: drop swim_info() function
> swim: encapsulate 'uint16' payload size inside swim.c
> swim: do not rebind when new 'port' is 0
> swim: set 'left' status in self on swim_quit()
> msgpack: allow to pass 'struct ibuf *' into encode()
> msgpack: allow to pass 'const char *' into decode()
> Drop an unused function and class
>
> src/box/lua/merger.c | 24 ++---------------
> src/lib/swim/swim.c | 29 ++++----------------
> src/lib/swim/swim.h | 9 ++-----
> src/lib/swim/swim_transport_udp.c | 14 ++++++++--
> src/lua/msgpack.c | 28 ++++++--------------
> src/lua/utils.c | 43 ++++++++++++++++++++++++++++++
> src/lua/utils.h | 44 +++++++++++++------------------
> test/app-tap/msgpack.test.lua | 7 ++---
> test/app/msgpack.result | 44 ++++++++++++++++++++++++++++++-
> test/app/msgpack.test.lua | 16 +++++++++++
> test/unit/swim.c | 20 +++++++++-----
> test/unit/swim.result | 21 ++++++++-------
> test/unit/swim_test_utils.c | 12 ++++-----
> test/unit/swim_test_utils.h | 6 ++---
> 14 files changed, 187 insertions(+), 130 deletions(-)
>
> --
> 2.20.1 (Apple Git-117)
>
>
prev parent reply other threads:[~2019-05-15 10:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 23:06 [tarantool-patches] " Vladislav Shpilevoy
2019-05-14 23:06 ` [tarantool-patches] [PATCH 1/7] swim: drop swim_info() function Vladislav Shpilevoy
2019-05-15 2:00 ` [tarantool-patches] " Konstantin Osipov
2019-05-14 23:06 ` [tarantool-patches] [PATCH 2/7] swim: encapsulate 'uint16' payload size inside swim.c Vladislav Shpilevoy
2019-05-15 2:02 ` [tarantool-patches] " Konstantin Osipov
2019-05-14 23:06 ` [tarantool-patches] [PATCH 3/7] swim: do not rebind when new 'port' is 0 Vladislav Shpilevoy
2019-05-15 2:02 ` [tarantool-patches] " Konstantin Osipov
2019-05-14 23:06 ` [tarantool-patches] [PATCH 4/7] swim: set 'left' status in self on swim_quit() Vladislav Shpilevoy
2019-05-15 2:03 ` [tarantool-patches] " Konstantin Osipov
2019-05-14 23:06 ` [tarantool-patches] [PATCH 5/7] msgpack: allow to pass 'struct ibuf *' into encode() Vladislav Shpilevoy
2019-05-15 2:05 ` [tarantool-patches] " Konstantin Osipov
2019-05-14 23:06 ` [tarantool-patches] [PATCH 6/7] msgpack: allow to pass 'const char *' into decode() Vladislav Shpilevoy
2019-05-15 2:05 ` [tarantool-patches] " Konstantin Osipov
2019-05-14 23:06 ` [tarantool-patches] [PATCH 7/7] Drop an unused function and class Vladislav Shpilevoy
2019-05-15 2:06 ` [tarantool-patches] " Konstantin Osipov
2019-05-15 10:02 ` Vladislav Shpilevoy [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=8f3025a1-257c-e810-ae18-c7fe8b8ef89d@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH 0/7] swim lua preparation, again' \
/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