From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH 3/3] maintainers: add stable mailing list
Date: Mon, 5 Dec 2016 09:39:24 +0100 [thread overview]
Message-ID: <64469bb9-ac40-2902-d8f5-ebf0b996158d@redhat.com> (raw)
In-Reply-To: <20161205043633.GH24403@yliu-dev.sh.intel.com>
On 12/05/2016 05:36 AM, Yuanhan Liu wrote:
> On Sun, Dec 04, 2016 at 04:36:36PM +0000, Mcnamara, John wrote:
>>
>>
>>> -----Original Message-----
>>> From: Yuanhan Liu [mailto:yuanhan.liu@linux.intel.com]
>>> Sent: Thursday, December 1, 2016 7:07 AM
>>> To: dev@dpdk.org
>>> Cc: Thomas Monjalon <thomas.monjalon@6wind.com>; Mcnamara, John
>>> <john.mcnamara@intel.com>; Yuanhan Liu <yuanhan.liu@linux.intel.com>
>>> Subject: [PATCH 3/3] maintainers: add stable mailing list
>>>
>>> Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
>>> ---
>>> MAINTAINERS | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 3df1754..076e86c 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -35,6 +35,7 @@ F: scripts/test-build.sh Stable Branches
>>> ---------------
>>> T: git://dpdk.org/dpdk-stable
>>> +M: stable@dpdk.org
>>
>> I acked this previously but looking at it again I'm not 100% sure that stable@dpdk.org
>> should be the maintainer.
>>
>> The glossary at the top of the file says:
>>
>> Descriptions of section entries:
>> M: Maintainer's Full Name <address@domain>
>>
>> So maybe the entry should have your name and also stable@dpdk.org on a separate line.
>> This would be clearer way of showing the stable release tree maintainer.
>
> I actually just meant to add the stable mailing list addr (as the
> subject says). Seems there are no such field for it?
"L: stable@dpdk.org" ?
This is how MLs are added in Kernel's MAINTAINER file.
Cheers,
Maxime
>
> --yliu
>
next prev parent reply other threads:[~2016-12-05 8:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 7:06 [dpdk-dev] [PATCH 0/3] maintainers: minor updates to virtio and stable Yuanhan Liu
2016-12-01 7:06 ` [dpdk-dev] [PATCH 1/3] maintainers: update virtio maintainer Yuanhan Liu
2016-12-01 15:17 ` Mcnamara, John
2016-12-01 7:06 ` [dpdk-dev] [PATCH 2/3] maintainers: update virtio section name Yuanhan Liu
2016-12-01 15:08 ` Thomas Monjalon
2016-12-01 15:18 ` Mcnamara, John
2016-12-01 7:06 ` [dpdk-dev] [PATCH 3/3] maintainers: add stable mailing list Yuanhan Liu
2016-12-01 15:18 ` Mcnamara, John
2016-12-04 16:36 ` Mcnamara, John
2016-12-05 4:36 ` Yuanhan Liu
2016-12-05 8:39 ` Maxime Coquelin [this message]
2017-01-12 6:24 ` [dpdk-dev] [PATCH v2 0/2] maintainers: minor updates to virtio/vhost Yuanhan Liu
2017-01-12 6:24 ` [dpdk-dev] [PATCH v2 1/2] maintainers: update virtio maintainer Yuanhan Liu
2017-01-12 6:24 ` [dpdk-dev] [PATCH v2 2/2] maintainers: split virtio and vhost Yuanhan Liu
2017-02-08 17:36 ` [dpdk-dev] [PATCH v2 0/2] maintainers: minor updates to virtio/vhost 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=64469bb9-ac40-2902-d8f5-ebf0b996158d@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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 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).