From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=d5a67dVUAW5yQivVOXf6v4drk7MPnwHp6UEbFdR6S34=; b=jJCDmpq8v9in3N43P+mCYdAPYG5r3QD9Kw51x8KOd4hFX+bjeRi2t8Dp/cM/7hptK4 pd3AnK8vuZKrYyC8/di5q9DrsUUwrc0CsxxbT0zRcUHo6Kv5RehO+u7KF9A/j5TibE5F ggAhVTiaogk75DWr6TMEdJci8opx2RqX/Qt+XgvMSUA8YYUQu9oEWjpk2c5jrNLVRZjG O07Vh2N1jITOX/Zh6qTh3UaXKxY5WjHZf9fUfspCsI82HRpjALO3Tvr00kLoezCWfRab bgYu/unU81zO79KJYA2vhywmpevbl6pLv+XyeovDtgpXIKpi+f5grp26tAiym/YcOyEE IqRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=d5a67dVUAW5yQivVOXf6v4drk7MPnwHp6UEbFdR6S34=; b=pnlfAUf3bzkRLlVKw6KAebeDkRQFHefCYARTIsFQYnZ75G7gwSBIugrIP6KkYD819Z Ke1OX757HAwF2p0kuf6M6lYJD5QrubEf7DYZVhWm7Jz39p29FBCNSKO+NkMDwModzztM JXHD4wtIlUHREPd9F7XVSWfkagXmB1bpGqSOP3nISGXAaifeBh2XzleY39qnsN0UgpLZ Powa7UmYsAS+dcnUbmDs0STZN3x0jMNB+FvlUnxmTogt83gBxLh5AoZDYvE3rWPk0QuA Uep80JgsrQsAuQeruT0hzVGbBLksGJoa/57hkdeEksMkpTtRkZG7D8zV22HNWS1RX8Yv 4m8g== X-Gm-Message-State: ALKqPwcYULdCCYePbEP1wT2e8DUNNHzPxahTYvsw1/F2R+Edsuk4gWX1 y2WUL4NfskDVlQmN331MLcI9vzCh X-Google-Smtp-Source: AB8JxZr4MNXP2I0HjFtK9ufb/qXOUR40mRt7oqa0JILCRsRZIhqDS6ZzeVHWMaRhgTQR3SlCtUsfqg== X-Received: by 2002:a1c:d046:: with SMTP id h67-v6mr1841870wmg.80.1526565219559; Thu, 17 May 2018 06:53:39 -0700 (PDT) Received: from localhost (slip139-92-244-193.lon.uk.prserv.net. [139.92.244.193]) by smtp.gmail.com with ESMTPSA id m35-v6sm5535464wrm.51.2018.05.17.06.53.38 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 17 May 2018 06:53:38 -0700 (PDT) From: luca.boccassi@gmail.com To: dev@dpdk.org Cc: yliu@fridaylinux.org, ktraynor@redhat.com, thomas@monjalon.net, Luca Boccassi Date: Thu, 17 May 2018 14:53:35 +0100 Message-Id: <20180517135335.14024-1-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.14.2 In-Reply-To: <20180516170538.21784-1-luca.boccassi@gmail.com> References: <20180516170538.21784-1-luca.boccassi@gmail.com> Subject: [dpdk-dev] [PATCH v3] doc: advise to specify LTS branch when backporting patches X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2018 13:53:40 -0000 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