From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 570E7A0350 for ; Tue, 30 Jun 2020 10:58:19 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 31DC51BF5D; Tue, 30 Jun 2020 10:58:19 +0200 (CEST) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id F3C061BF5C for ; Tue, 30 Jun 2020 10:58:17 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 9FE90643; Tue, 30 Jun 2020 04:58:15 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Tue, 30 Jun 2020 04:58:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:subject:date:message-id:mime-version :content-transfer-encoding; s=fm1; bh=LiFmJugGDLnb/jhTaogtCyUlh2 CReDQLgsIs9Dxsp9U=; b=ayD5aMbn/rlRAYIYTc3gqZbm9Tf/6fXV1OyGT+eVkk WagF/H9C46sDakMNTI0ToHzKUg31aO8gsuRkPnO8yFNmcegblWi+/LjXL2lnz4+X ZWsFsVtT7SX0UI+2oS0XM7gukVk6JFUc7xcitEkEjmrZ45bP/ZP6dkNJJPAt8rlA M4HHf31Sd/NI6JCkEq1kTbjl5XpSo/g4CDBz11b9Mzmy+c1TLinBx0qAwtppw8+o 2hMS2mz9kpAGGaPG3Tb1cVzWmI4mMkdfa9D9sVBu3xPzbbpLBdIoVznPYWfebExH KoOLZLb4l3U9FQIxyeoufYI2qBLzrLM+0xsrsgLtJZCg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:date:from :message-id:mime-version:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=LiFmJugGDLnb/jhTa ogtCyUlh2CReDQLgsIs9Dxsp9U=; b=JfIwCl4xMntGOMJbGEgkPTUhQwK7ihxA+ QlbDl9gi1BDFHitjO4Z1aQWqjDROKREkNxpVjfUDGjGFHTZ4eZ0K5HAfnClTbSYf KevjY5FTKZJu1smMgacv+JElJEDwcMRGvVUp88V7uNBDg28eCIJbo20kiPtdViBb Em3Kkg5qKAstdUESZm7/WtOvGBMOggcbhuZjB1P7QWDDrM1g4cKWW8Ifmo3JiNRe +VAOezaUn5fEziASGc53dNQJ92w0rkNWMPxY6sPIssn+YqVjem0K1R9cbw6derdb zIwYrM4Bg7Hg93FQXlhp11M2ktdqu51E7wFOnVWp6XsVXwdLRtkRw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrvddtuddgtdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkofgggfestdekredtre dttdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhho nhhjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpeeutdeftedtudehieejgfejje ehjefffedvhefhhffgffejhefgffetjefgkedtgfenucffohhmrghinhepkhgvrhhnvghl rdhorhhgnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhn rdhnvght X-ME-Proxy: Received: from xps.monjalon.net (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 4F66C30600AA for ; Tue, 30 Jun 2020 04:58:14 -0400 (EDT) From: Thomas Monjalon To: web@dpdk.org Date: Tue, 30 Jun 2020 10:58:02 +0200 Message-Id: <20200630085802.1035628-1-thomas@monjalon.net> X-Mailer: git-send-email 2.26.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-web] [PATCH] update patch submission process X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: web-bounces@dpdk.org Sender: "web" Add --cc-cmd devtools/get-maintainer.sh Recommend threading based on the first patch or cover letter. Add list of commit log tags. Signed-off-by: Thomas Monjalon --- content/contribute/_index.md | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/content/contribute/_index.md b/content/contribute/_index.md index 5afc23c..e815b0e 100644 --- a/content/contribute/_index.md +++ b/content/contribute/_index.md @@ -57,6 +57,13 @@ The email title must begin with *[PATCH]* to distinguish it among discussions. There must be details in the commit log, explaining what was the problem and how it is fixed.\ When fixing a regression, it is a good idea to reference the id of the commit which introduced the bug (see fixline alias below). +Few tags are standardized: +``` +Coverity issue: +Bugzilla ID: +Fixes: +Cc: stable@dpdk.org +``` Before sending a patch, be sure that there is no licensing issue. The commit log must have a *Signed-off-by* line (*--signoff* option). @@ -70,14 +77,14 @@ It is automatically or manually prepared in the right format by [git format-patch](http://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html). Typical usage is: ``` -git send-email -1 --to dev@dpdk.org +git send-email -1 --to dev@dpdk.org --cc-cmd devtools/get-maintainer.sh ``` If a previous version of the patch has already been sent, a version number and changelog annotations are helpful: ``` -git send-email -1 -v2 --annotate --in-reply-to ---to dev@dpdk.org --cc +git send-email -1 -v2 --annotate --in-reply-to +--to dev@dpdk.org --cc-cmd devtools/get-maintainer.sh --cc ``` Annotations take place after the 3 dashes and should explicit @@ -88,11 +95,12 @@ The Message-ID can be found in the email header of the previous patch or in its In the case of a bug reported on the mailing list, the patch should be a reply to the bug report. -An updated patchset should be a reply to the previous cover letter. +An updated patchset should be a reply to the first cover letter. When sending several patches in a series, a cover letter may explain the global idea: ``` -git send-email -3 --to dev@dpdk.org --cover-letter --annotate +git send-email -3 --to dev@dpdk.org --cc-cmd devtools/get-maintainer.sh +--cover-letter --annotate ``` Shallow threading (*--thread --no-chain-reply-to*) is preferred for patch series. -- 2.26.2