Tarantool development patches archive
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Vladimir Davydov <vdavydov.dev@gmail.com>
Cc: tarantool-patches@freelists.org,
	"Георгий Кириченко" <georgy@tarantool.org>
Subject: Re: [tarantool-patches] [PATCH v2] lua/fiber: Fix abort on malformed join input
Date: Mon, 25 Feb 2019 16:12:24 +0300	[thread overview]
Message-ID: <20190225131224.GE7198@uranus> (raw)
In-Reply-To: <20190225125412.6cepuqwvdiutmdvt@esperanza>

On Mon, Feb 25, 2019 at 03:54:12PM +0300, Vladimir Davydov wrote:
> We don't include changelog in the commit message. Please put it after
> the diff separator (---) so that it is ignored by git-am.

Sure!

> > Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
> 
> We don't sign-off patches :-)

Sure, it is not a problem to not put sob into patches.

      reply	other threads:[~2019-02-25 13:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23 13:34 Cyrill Gorcunov
2019-02-23 19:49 ` [tarantool-patches] " Георгий Кириченко
2019-02-25 12:54 ` [tarantool-patches] " Vladimir Davydov
2019-02-25 13:12   ` 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=20190225131224.GE7198@uranus \
    --to=gorcunov@gmail.com \
    --cc=georgy@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=vdavydov.dev@gmail.com \
    --subject='Re: [tarantool-patches] [PATCH v2] lua/fiber: Fix abort on malformed join input' \
    /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