From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Traynor Subject: Re: [PATCH v2] doc: advise to specify LTS branch when backporting patches Date: Wed, 16 May 2018 20:45:48 +0100 Message-ID: References: <20180516143134.24838-1-luca.boccassi@gmail.com> <20180516170538.21784-1-luca.boccassi@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: yliu@fridaylinux.org, thomas@monjalon.net, Luca Boccassi To: luca.boccassi@gmail.com, dev@dpdk.org Return-path: Received: from mx1.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by dpdk.org (Postfix) with ESMTP id 2020EAAEB for ; Wed, 16 May 2018 21:45:51 +0200 (CEST) In-Reply-To: <20180516170538.21784-1-luca.boccassi@gmail.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 05/16/2018 06:05 PM, luca.boccassi@gmail.com wrote: > From: Luca Boccassi > > We have many stable branches being maintained at the same time, and > sometimes it's not clear which branch a patch is being backported for. > Note in the guidelines that it should be specified via the cover letter, > annotation or using --subject-prefix. > Also note to send only to stable@dpdk.org, not dev@dpdk.org. > Acked-by: Kevin Traynor > Signed-off-by: Luca Boccassi > --- > > v2: hint that --subject-prefix is required, fix typos > > doc/guides/contributing/patches.rst | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst > index 2287835f9..47c41288e 100644 > --- a/doc/guides/contributing/patches.rst > +++ b/doc/guides/contributing/patches.rst > @@ -450,6 +450,14 @@ Experienced committers may send patches directly with ``git send-email`` without > The options ``--annotate`` and ``confirm = always`` are recommended for checking patches before sending. > > > +Backporting patches for Stable Releases > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + > +Sometimes a maintainer or contributor wishes, or can be asked, to send a patch for a stable release rather than mainline. In this case the patch(es) should be sent to ``stable@dpdk.org``, not to ``dev@dpdk.org``. > + > +Given that there are multiple stable releases being maintained at the same time, please specify exactly which branch(es) the patch is for using ``git send-email --subject-prefix='16.11' ...`` and also optionally in the cover letter or in the annotation. > + > + > The Review Process > ------------------ > >