From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
dev@dpdk.org,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Markos Chandras <mchandras@suse.de>,
Panu Matilainen <pmatilai@redhat.com>
Subject: Re: [dpdk-dev] RFC: DPDK Long Term Support
Date: Mon, 06 Jun 2016 15:31:09 +0200 [thread overview]
Message-ID: <12523923.duYttjjiSP@xps13> (raw)
In-Reply-To: <20160606114924.GC10038@yliu-dev.sh.intel.com>
2016-06-06 19:49, Yuanhan Liu:
> On Fri, Jun 03, 2016 at 06:05:15PM +0200, Thomas Monjalon wrote:
> > 2016-06-03 15:07, Mcnamara, John:
> > > Developers submitting fixes to the mainline should also CC the maintainer so
> > > that they can evaluate the patch. A <stable@dpdk.org> email address could be
> > > provided for this so that it can be included as a CC in the commit messages
> > > and documented in the Code Contribution Guidelines.
> >
> > Why?
> > We must avoid putting too much restrictions on the contributors.
>
> This is actually requested by me, in a behaviour similar to Linux
> kernel community takes. Here is the thing, the developer normally
> knows better than a generic maintainer (assume it's me) that a patch
> applies to stable branch or not. This is especially true for DPDK,
> since we ask the developer to note down the bug commit by adding a
> fix line.
>
> It wouldn't be a burden for an active contributor, as CCing to related
> people (including right mailing list) is a good habit they already
> have. For some one-time contributors, it's okay that they don't know
> and follow it.
>
> In such case, I guess we need the help from the related subsystem
> maintainer: if it's a good bug fix that applies to stable branch,
> and the contributor forgot to make a explicit cc to stable mailing
> list, the subsystem maintainer should forward or ask him to forward
> to stable mailing list.
>
> The reason I'm asking is that as a generic maintainer, there is
> simply no such energy to keep an eye on all patches: you have to
> be aware of that we have thoughts of email per month from dpdk dev
> mailing list: the number of last month is 1808.
>
> Doing so would allow one person maintain several stable tree
> be possible.
>
> For more info, you could check linux/Documentation/stable_kernel_rules.txt.
Makes sense to CC stable@dpdk.org list (must be created).
Why put a CC tag in the commit? For automatic processing?
Maybe it is too early to run before walking ;)
next prev parent reply other threads:[~2016-06-06 13:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 15:07 Mcnamara, John
2016-06-03 16:05 ` Thomas Monjalon
2016-06-06 11:49 ` Yuanhan Liu
2016-06-06 13:31 ` Thomas Monjalon [this message]
2016-06-06 14:14 ` Yuanhan Liu
2016-06-06 14:23 ` Thomas Monjalon
2016-06-07 13:17 ` Mcnamara, John
2016-06-03 18:17 ` Matthew Hall
2016-06-07 12:53 ` Mcnamara, John
2016-06-05 18:15 ` Neil Horman
2016-06-06 9:27 ` Thomas Monjalon
2016-06-06 13:47 ` Neil Horman
2016-06-06 14:21 ` Thomas Monjalon
2016-06-06 15:07 ` Neil Horman
2016-06-07 16:21 ` Mcnamara, John
2016-06-07 15:55 ` Mcnamara, John
2016-06-06 13:44 ` Nirmoy Das
2016-06-06 14:16 ` Yuanhan Liu
2016-06-07 12:36 ` Christian Ehrhardt
2016-06-07 19:39 ` Martinx - ジェームズ
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=12523923.duYttjjiSP@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=mchandras@suse.de \
--cc=pmatilai@redhat.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).