DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] devtools: relax tag checking in fixes
Date: Wed, 18 Jan 2017 16:52:48 +0100	[thread overview]
Message-ID: <11885475.JgnvjXF21Z@xps13> (raw)
In-Reply-To: <20170118100418.GS10293@yliu-dev.sh.intel.com>

2017-01-18 18:04, Yuanhan Liu:
> On Wed, Jan 18, 2017 at 10:37:52AM +0100, Thomas Monjalon wrote:
> > The tag "Cc: stable@dpdk.org" must be set when the commit must be
> > backported to a stable branch. The reminder is reworded.
> > 
> > It should be located just below the "Fixes:" tag (without blank line)
> > and followed by a blank line, separated from SoB and review tags below.
> > However, there is no strong need for checking blank lines.
> > 
> > Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> 
> Reviewed-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
> 
> Thanks!

Applied

      reply	other threads:[~2017-01-18 15:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 14:54 [dpdk-dev] [PATCH] devtools: check stable tag " Thomas Monjalon
2017-01-17 18:15 ` Ferruh Yigit
2017-01-17 18:42   ` Thomas Monjalon
2017-01-18  4:41     ` Yuanhan Liu
2017-01-18  8:32       ` Thomas Monjalon
2017-01-18  8:54         ` Yuanhan Liu
2017-01-18 17:25       ` Ferruh Yigit
2017-01-19  8:05         ` Yuanhan Liu
2017-01-19 12:00           ` Ferruh Yigit
2017-01-20  7:59             ` Yuanhan Liu
2017-01-20 10:10               ` Thomas Monjalon
2017-01-20 10:23                 ` Yuanhan Liu
2017-01-20 16:20                   ` Ferruh Yigit
2017-01-18  9:37 ` [dpdk-dev] [PATCH v2] devtools: relax tag checking " Thomas Monjalon
2017-01-18 10:04   ` Yuanhan Liu
2017-01-18 15:52     ` Thomas Monjalon [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=11885475.JgnvjXF21Z@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=yuanhan.liu@linux.intel.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).