From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] doc: add guides for patch fix issues Date: Tue, 29 May 2018 17:24:43 +0200 Message-ID: <6140320.jqdv53SyBi@xps> References: <20180528152342.22467-1-marko.kovacevic@intel.com> <20180529110124.35666-1-marko.kovacevic@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, ferruh.yigit@intel.com, john.mcnamara@intel.com To: Marko Kovacevic Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 9EAACDE0 for ; Tue, 29 May 2018 17:24:45 +0200 (CEST) In-Reply-To: <20180529110124.35666-1-marko.kovacevic@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 29/05/2018 13:01, Marko Kovacevic: > Added contribution guideline for adding tags > when sending patches that have been raised on > Bugzilla > > Signed-off-by: Marko Kovacevic > Acked-by: Ferruh Yigit Applied, thanks. Note: I have re-wrapped the text below: > +`Bugzilla `_ > +is a bug- or issue-tracking system. Bug-tracking > +systems allow individual or groups of developers effectively to keep track of outstanding > +problems with their product. When fixing an issue raised in Bugzilla, the patch must contain > +a Bugzilla issue ID in the body of the commit message. For example:: to be more logically split: +`Bugzilla `_ +is a bug- or issue-tracking system. +Bug-tracking systems allow individual or groups of developers +effectively to keep track of outstanding problems with their product. +When fixing an issue raised in Bugzilla, the patch must contain +a Bugzilla issue ID in the body of the commit message. +For example:: It think such wrapping should be preferred because it allows to change or remove a sentence without disturbing the other ones.