Tarantool development patches archive
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: tml <tarantool-patches@dev.tarantool.org>
Subject: [Tarantool-patches] [PATCH v11 0/3] popen: Introduce backend engine
Date: Mon, 17 Feb 2020 15:18:15 +0300	[thread overview]
Message-ID: <20200217121818.11375-1-gorcunov@gmail.com> (raw)

In v11 I cleaned up some nits and updated the tests.

issue https://github.com/tarantool/tarantool/issues/4031
branch https://github.com/tarantool/tarantool/tree/gorcunov/gh-4031-popen-11

Cyrill Gorcunov (3):
  coio: export helpers
  popen: introduce a backend engine
  test: unit/popen

 src/box/applier.cc          |    2 +-
 src/lib/core/CMakeLists.txt |    1 +
 src/lib/core/coio.h         |   18 +-
 src/lib/core/popen.c        | 1061 +++++++++++++++++++++++++++++++++++
 src/lib/core/popen.h        |  191 +++++++
 src/main.cc                 |    4 +
 test/unit/CMakeLists.txt    |    3 +
 test/unit/popen.c           |  253 +++++++++
 test/unit/popen.result      |   28 +
 9 files changed, 1555 insertions(+), 6 deletions(-)
 create mode 100644 src/lib/core/popen.c
 create mode 100644 src/lib/core/popen.h
 create mode 100644 test/unit/popen.c
 create mode 100644 test/unit/popen.result


base-commit: f54f4dc03afcc9b34261e6275881f0120faef67e
-- 
2.20.1

             reply	other threads:[~2020-02-17 12:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 12:18 Cyrill Gorcunov [this message]
2020-02-17 12:18 ` [Tarantool-patches] [PATCH v11 1/3] coio: export helpers Cyrill Gorcunov
2020-02-17 12:18 ` [Tarantool-patches] [PATCH v11 2/3] popen: introduce a backend engine Cyrill Gorcunov
2020-02-17 12:18 ` [Tarantool-patches] [PATCH v11 3/3] test: unit/popen Cyrill Gorcunov
2020-02-27 22:47 ` [Tarantool-patches] [PATCH v11 0/3] popen: Introduce backend engine Kirill Yukhin

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=20200217121818.11375-1-gorcunov@gmail.com \
    --to=gorcunov@gmail.com \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v11 0/3] popen: Introduce backend engine' \
    /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