All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>,
	Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, pablo.de.lara.guarch@intel.com, bruce.richardson@intel.com
Subject: Re: [PATCH] devtools: check stable tag in fixes
Date: Fri, 20 Jan 2017 16:20:45 +0000	[thread overview]
Message-ID: <0450d62c-dcb2-a1d8-dded-550f2308a501@intel.com> (raw)
In-Reply-To: <20170120102326.GX10293@yliu-dev.sh.intel.com>

On 1/20/2017 10:23 AM, Yuanhan Liu wrote:
> On Fri, Jan 20, 2017 at 11:10:54AM +0100, Thomas Monjalon wrote:
>> 2017-01-20 15:59, Yuanhan Liu:
>>> On Thu, Jan 19, 2017 at 12:00:23PM +0000, Ferruh Yigit wrote:
>>>> To highlight, and double check, the process will be updated as following:
>>>>
>>>> - Author may or may not have "CC: stable@dpdk.org" for fixes.
>>>>
>>>> - Maintainer/Committer may add "CC: stable@dpdk.org" tag to commit log,
>>>> but won't send a mail to the stable mail list.
>>>>
>>>> - "CC: stable@dpdk.org" tags will remain in commit logs.
>>>
>>> Yes.
>>
>> Sorry, I do not understand why a maintainer or a committer would not send a
>> mail to the stable ML. If we add the CC: tag, we can also CC:stable@dpdk.org
>> in our reply.
> 
> Oh, right.

Because if the decision will be given based on parsing git history, same
patch being sent to stable mail list will be duplicate and will create
noise.
But if this will help somebody, somehow, I don't see any issue to
sending mail to stable mail list.

> 
> 	--yliu
> 

  reply	other threads:[~2017-01-20 16:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 14:54 [PATCH] devtools: check stable tag in fixes 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 [this message]
2017-01-18  9:37 ` [PATCH v2] devtools: relax tag checking " Thomas Monjalon
2017-01-18 10:04   ` Yuanhan Liu
2017-01-18 15:52     ` Thomas Monjalon

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=0450d62c-dcb2-a1d8-dded-550f2308a501@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=thomas.monjalon@6wind.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.