From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-f66.google.com (mail-lf1-f66.google.com [209.85.167.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 7CB64469719 for ; Fri, 14 Feb 2020 10:07:16 +0300 (MSK) Received: by mail-lf1-f66.google.com with SMTP id c23so6061695lfi.7 for ; Thu, 13 Feb 2020 23:07:16 -0800 (PST) Date: Fri, 14 Feb 2020 10:07:13 +0300 From: Cyrill Gorcunov Message-ID: <20200214070713.GR21061@uranus> References: <20200213205618.7982-1-gorcunov@gmail.com> <1bec5998-d6de-e549-3883-ae21ab071ce3@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1bec5998-d6de-e549-3883-ae21ab071ce3@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH v7 0/2] fiber: Handle stack madvise/mprotect errors List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladislav Shpilevoy Cc: tml 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.