From mboxrd@z Thu Jan 1 00:00:00 1970 From: luca.boccassi@gmail.com Subject: [PATCH v3] doc: advise to specify LTS branch when backporting patches Date: Thu, 17 May 2018 14:53:35 +0100 Message-ID: <20180517135335.14024-1-luca.boccassi@gmail.com> References: <20180516170538.21784-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-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by dpdk.org (Postfix) with ESMTP id 3A0256CD3 for ; Thu, 17 May 2018 15:53:40 +0200 (CEST) Received: by mail-wm0-f43.google.com with SMTP id l1-v6so9298223wmb.2 for ; Thu, 17 May 2018 06:53:40 -0700 (PDT) In-Reply-To: <20180516170538.21784-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 --- v3: break long lines, fix subject-prefix argument to include PATH v2: hint that --subject-prefix is required, fix typos doc/guides/contributing/patches.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst index 2287835f9..c077e341a 100644 --- a/doc/guides/contributing/patches.rst +++ b/doc/guides/contributing/patches.rst @@ -450,6 +450,18 @@ 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='PATCH 16.11' ...`` +and also optionally in the cover letter or in the annotation. + + The Review Process ------------------ -- 2.14.2