From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tml <tarantool-patches@dev.tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH v7 0/2] fiber: Handle stack madvise/mprotect errors
Date: Fri, 14 Feb 2020 10:07:13 +0300 [thread overview]
Message-ID: <20200214070713.GR21061@uranus> (raw)
In-Reply-To: <1bec5998-d6de-e549-3883-ae21ab071ce3@tarantool.org>
On Fri, Feb 14, 2020 at 12:26:05AM +0100, Vladislav Shpilevoy wrote:
> Thanks for the fixes!
>
> Please, put branch and issue link here next time.
> It is really hard to find that branch just by commit
> title, or by searching for older versions of the
> branch in email history. Especially taking into
> account that there are 7 versions of mprotect branches.
I did so in reply to this email ('cause I managed to forgot, sorry)
>
> Btw, you can force push into one branch, it is ok, and
> is even more convenient. At least from reviewer's point
> of view.
prev parent reply other threads:[~2020-02-14 7:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 20:56 Cyrill Gorcunov
2020-02-13 20:56 ` [Tarantool-patches] [PATCH v7 1/2] fiber: set diagnostics at madvise/mprotect failure Cyrill Gorcunov
2020-02-13 23:26 ` Vladislav Shpilevoy
2020-02-14 7:54 ` Cyrill Gorcunov
2020-02-14 22:27 ` Vladislav Shpilevoy
2020-02-15 6:57 ` Cyrill Gorcunov
2020-02-15 15:41 ` Vladislav Shpilevoy
2020-02-15 17:55 ` Cyrill Gorcunov
2020-02-13 20:56 ` [Tarantool-patches] [PATCH v7 2/2] fiber: leak slab if unable to bring prots back Cyrill Gorcunov
2020-02-13 23:26 ` Vladislav Shpilevoy
2020-02-14 8:25 ` Cyrill Gorcunov
2020-02-13 20:57 ` [Tarantool-patches] [PATCH v7 0/2] fiber: Handle stack madvise/mprotect errors Cyrill Gorcunov
2020-02-13 23:26 ` Vladislav Shpilevoy
2020-02-14 7:07 ` Cyrill Gorcunov [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=20200214070713.GR21061@uranus \
--to=gorcunov@gmail.com \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v7 0/2] fiber: Handle stack madvise/mprotect errors' \
/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