From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 789DF2BF9 for ; Wed, 30 Mar 2016 16:46:43 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 30 Mar 2016 07:46:34 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,416,1455004800"; d="scan'208";a="934754311" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.52]) by fmsmga001.fm.intel.com with SMTP; 30 Mar 2016 07:46:32 -0700 Received: by (sSMTP sendmail emulation); Wed, 30 Mar 2016 15:46:31 +0025 Date: Wed, 30 Mar 2016 15:46:31 +0100 From: Bruce Richardson To: Yuanhan Liu Cc: Thomas Monjalon , dev@dpdk.org Message-ID: <20160330144631.GD21156@bricha3-MOBL3> References: <1459286986-31148-1-git-send-email-thomas.monjalon@6wind.com> <20160330014634.GC3080@yliu-dev.sh.intel.com> <20160330142740.GB21156@bricha3-MOBL3> <20160330144414.GD3080@yliu-dev.sh.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160330144414.GD3080@yliu-dev.sh.intel.com> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH] scripts: check commit formatting X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2016 14:46:43 -0000 On Wed, Mar 30, 2016 at 10:44:14PM +0800, Yuanhan Liu wrote: > On Wed, Mar 30, 2016 at 03:27:40PM +0100, Bruce Richardson wrote: > > On Wed, Mar 30, 2016 at 09:46:34AM +0800, Yuanhan Liu wrote: > > > On Tue, Mar 29, 2016 at 11:29:46PM +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. > > > > > > Actually, I think we might be able to do 2 tests here: > > > > > > - space line between paragraphs. > > > > > > - lines over 80 chars. > > > > 75 chars for commit messages, and 50 for commit titles :-) > > I'd agree that 75 char is better. My personal preference is actually > 68 :) > I just go with what vim uses on my machine, because vim is always right :-)