From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41]) by dpdk.org (Postfix) with ESMTP id E06F82B92 for ; Mon, 6 Jun 2016 15:31:10 +0200 (CEST) Received: by mail-wm0-f41.google.com with SMTP id m124so72497500wme.1 for ; Mon, 06 Jun 2016 06:31:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=uvElyvIaLdaYw4RxW+Hn4uXFdHQVdKKDjVTHOyaA6l0=; b=XoApDw8cjJMx88xewqA/gLmIlbq9Fhj6l+Mh2rnWmuqNynJbmC5Q+9R0H+AUFO6MHh m8DavnCWLbDDrex7kb6NKqHyMi6G64NGyT1JmU56hCPr4ekxhdyIH+g+yDsnGSJ/eE/T kVE2TyD32P9agnZ136a7aPAiYsk3uNQZdYaUJ9lY9oDAL+rnxlX3lkBuy2KQ0+Vxt7S+ O/1yoB9jHV0MLa3I5u6jqf3ZFjsnW91EBmsq6drmZKbePqpB0HcxOmgfK6/4Oc+NdWye Paw/P25raSiC85mMYK0gsNrrWLwr8mBKkRnYOit5K06D1rcCxeNlO2ZZupBjyANY2xB5 C0zQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=uvElyvIaLdaYw4RxW+Hn4uXFdHQVdKKDjVTHOyaA6l0=; b=O/yUoaBasYyZUCYV6sN2zCKDAe0Opm9j6Zmm5vkUOy1qNywPDiy4P4ZM8VUMadzmwo h//GwmXxpPMbZ/nkMB8RgBZ/aER9FLGN4D9nvgZqDKysW+8CaQ0GZ0nhz7AWSTY/IZta O12DSPmS5D9qBoC9+6fhpq737Dg1Rko4yLoi2Yka0opPpvIgvt1zBBW+4Ir65cTTw6X9 KIgNIapkyhEeftw21kruk55lMAXGUz/fM1Nihm+4x52nqE+nIW1oHlqEachDnPU9sd9n ofcJKzT6u6fArn0vcvl6Qp3bKxthlH6jbwhivSu1OX7y6R7S7XAHXc28sL2oM4yUa7fw 4GnQ== X-Gm-Message-State: ALyK8tKDbI03X2oPj4K1CZY34gZ0noLwPs3Dgfxp+5X/GmBqkQ5eG8bGpcW0kxcn+wcErmm/ X-Received: by 10.28.17.3 with SMTP id 3mr12925867wmr.94.1465219870587; Mon, 06 Jun 2016 06:31:10 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id lf7sm20304584wjb.23.2016.06.06.06.31.09 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 06 Jun 2016 06:31:09 -0700 (PDT) From: Thomas Monjalon To: Yuanhan Liu Cc: "Mcnamara, John" , dev@dpdk.org, Christian Ehrhardt , Markos Chandras , Panu Matilainen Date: Mon, 06 Jun 2016 15:31:09 +0200 Message-ID: <12523923.duYttjjiSP@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <20160606114924.GC10038@yliu-dev.sh.intel.com> References: <2142445.VVEujR2XLL@xps13> <20160606114924.GC10038@yliu-dev.sh.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] RFC: DPDK Long Term Support X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2016 13:31:11 -0000 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 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 ;)