From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id A442B532C for ; Wed, 12 Jul 2017 15:39:14 +0200 (CEST) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga105.jf.intel.com with ESMTP; 12 Jul 2017 06:39:13 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.40,350,1496127600"; d="scan'208";a="124267173" Received: from silpixa00398672.ir.intel.com ([10.237.223.128]) by orsmga005.jf.intel.com with ESMTP; 12 Jul 2017 06:39:02 -0700 From: Harry van Haaren To: dev@dpdk.org Cc: thomas@monjalon.net, Harry van Haaren Date: Wed, 12 Jul 2017 14:38:52 +0100 Message-Id: <1499866732-17085-1-git-send-email-harry.van.haaren@intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: References: Subject: [dpdk-dev] [PATCH] doc: add author on cc to git fixline alias 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: Wed, 12 Jul 2017 13:39:15 -0000 With this commit, the correct method to use git fixline to indicate a fix of a previous commit has changed. The new rules require the author of the original code that is being fixed to be on CC. The logic behind this improvement is that if there is a genuine bug, one of the ideal people to review is the author of the original code being fixed. Adding them on Cc makes them aware of the patch, avoiding it from being passed by accidentally while reading the mailing-list. Given that the original author (now on Cc:) might not actually review, there is no value in keeping the Cc: in git commit history. If the original author performs a review, their Reviewed-by: or Acked-by: is stored in git history (same as now). Signed-off-by: Harry van Haaren --- This fixline suggestion was proposed here: http://dpdk.org/ml/archives/dev/2017-July/071107.html Based on Thomas' feedback, improved CC: to Cc, and added note about removing the Cc: from git history. http://dpdk.org/ml/archives/dev/2017-July/071119.html --- doc/guides/contributing/patches.rst | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst index 7926c96..27e218b 100644 --- a/doc/guides/contributing/patches.rst +++ b/doc/guides/contributing/patches.rst @@ -207,18 +207,21 @@ Here are some guidelines for the body of a commit message: * The text of the commit message should be wrapped at 72 characters. -* When fixing a regression, it is a good idea to reference the id of the commit which introduced the bug. - You can generate the required text using the following git alias:: +* When fixing a regression, it is required to reference the id of the commit + which introduced the bug, and put the original author of that commit on CC. + You can generate the required lines using the following git alias, which prints + the commit SHA and the author of the original code:: - git config alias.fixline "log -1 --abbrev=12 --format='Fixes: %h (\"%s\")'" + git config alias.fixline "log -1 --abbrev=12 --format='Fixes: %h (\"%s\")%nCc: %ae'" - The ``Fixes:`` line can then be added to the commit message:: + The output of ``git fixline `` must then be added to the commit message:: - doc: fix vhost sample parameter + doc: fix some parameter description - Update the docs to reflect removed dev-index. + Update the docs, fixing description of some parameter. - Fixes: 17b8320a3e11 ("vhost: remove index parameter") + Fixes: abcdefgh1234 ("doc: add some parameter") + Cc: author@example.com Signed-off-by: Alex Smith -- 2.7.4