From mboxrd@z Thu Jan 1 00:00:00 1970 From: luca.boccassi@gmail.com Subject: [PATCH v2] doc: advise to specify LTS branch when backporting patches Date: Wed, 16 May 2018 18:05:38 +0100 Message-ID: <20180516170538.21784-1-luca.boccassi@gmail.com> References: <20180516143134.24838-1-luca.boccassi@gmail.com> Cc: yliu@fridaylinux.org, ktraynor@redhat.com, thomas@monjalon.net, Luca Boccassi To: dev@dpdk.org Return-path: Received: from mail-wr0-f196.google.com (mail-wr0-f196.google.com [209.85.128.196]) by dpdk.org (Postfix) with ESMTP id AEBD6D149 for ; Wed, 16 May 2018 19:05:45 +0200 (CEST) Received: by mail-wr0-f196.google.com with SMTP id 94-v6so2242190wrf.5 for ; Wed, 16 May 2018 10:05:45 -0700 (PDT) In-Reply-To: <20180516143134.24838-1-luca.boccassi@gmail.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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. 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 ------------------ -- 2.14.2