From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <yuanhan.liu@linux.intel.com>
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93])
 by dpdk.org (Postfix) with ESMTP id 0E6F92E83
 for <dev@dpdk.org>; Mon, 11 Apr 2016 18:11:08 +0200 (CEST)
Received: from fmsmga004.fm.intel.com ([10.253.24.48])
 by fmsmga102.fm.intel.com with ESMTP; 11 Apr 2016 09:11:08 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.24,462,1455004800"; d="scan'208";a="83101954"
Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.191])
 by fmsmga004.fm.intel.com with ESMTP; 11 Apr 2016 09:11:08 -0700
Date: Tue, 12 Apr 2016 00:13:42 +0800
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Message-ID: <20160411161342.GG3080@yliu-dev.sh.intel.com>
References: <1459286986-31148-1-git-send-email-thomas.monjalon@6wind.com>
 <1460389145-5570-1-git-send-email-thomas.monjalon@6wind.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1460389145-5570-1-git-send-email-thomas.monjalon@6wind.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Subject: Re: [dpdk-dev] [PATCH v2] scripts: check commit formatting
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Apr 2016 16:11:09 -0000

On Mon, Apr 11, 2016 at 05:39:05PM +0200, Thomas Monjalon wrote:
> The git messages have three parts:
> 1/ the headline
> 2/ the explanations
> 3/ the footer tags
> 
> The headline helps to quickly browse an history or catch instantly the
> purpose of a commit. Making it short with some consistent wording
> allows to easily parse it or match some patterns.
> 
> The explanations must give some keys like the reason of the change.
> Nothing can be automatically checked for this part, except line length.
> 
> The footer contains some tags to find the origin of a bug or who
> was working on it.
> 
> This script is doing some basic checks mostly on parts 1 and 3.
> 
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>

Reviewed-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>

	--yliu