From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org
Cc: kostja@tarantool.org
Subject: [tarantool-patches] Re: [PATCH 0/5] swim dissemination component
Date: Tue, 9 Apr 2019 15:25:23 +0300 [thread overview]
Message-ID: <bb6c1dfb-917a-b659-2f85-cb65ccc226cd@tarantool.org> (raw)
In-Reply-To: <cover.1554465150.git.v.shpilevoy@tarantool.org>
As I see, you've already pushed the old patchset, with
*two* commits above with review fixes, and without the
fixes you requested earlier. It reminds me this 'patchset':
73237320d8e40f8d4244c90ca4182f850c7cb402,
'sio: remove exceptions'. Good job. Well done. After all,
'git' is just an FTP client, right? It is not supposed to
push atomic and clean patches, to be able to use 'git blame',
to revert changes.
Talking of the mailing list, and our SOP on how to review
and push patches - they does not matter too. Great.
prev parent reply other threads:[~2019-04-09 12:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 11:57 [tarantool-patches] " Vladislav Shpilevoy
2019-04-05 11:57 ` [tarantool-patches] [PATCH 1/5] swim: encapsulate member bin info into a 'passport' Vladislav Shpilevoy
2019-04-05 11:57 ` [tarantool-patches] [PATCH 2/5] swim: make members array decoder be a separate function Vladislav Shpilevoy
2019-04-05 11:57 ` [tarantool-patches] [PATCH 3/5] test: speed up swim big cluster failure detection Vladislav Shpilevoy
2019-04-09 8:43 ` [tarantool-patches] " Konstantin Osipov
2019-04-09 11:47 ` Vladislav Shpilevoy
2019-04-05 11:57 ` [tarantool-patches] [PATCH 4/5] test: set packet drop rate instead of flag in swim tests Vladislav Shpilevoy
2019-04-05 11:57 ` [tarantool-patches] [PATCH 5/5] swim: introduce dissemination component Vladislav Shpilevoy
2019-04-08 20:13 ` [tarantool-patches] " Vladislav Shpilevoy
2019-04-09 9:58 ` Konstantin Osipov
2019-04-09 11:47 ` Vladislav Shpilevoy
2019-04-09 12:25 ` 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=bb6c1dfb-917a-b659-2f85-cb65ccc226cd@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH 0/5] swim dissemination component' \
/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