From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 228D821C7D; Tue, 29 May 2018 11:24:45 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 29 May 2018 11:24:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=x8O/Fr5KKdQsu5P1ynz+Cb29hN 5tV5dHnES7Q29hjuM=; b=J2zaTmeAn9CZsiCEFiZSwswtfOXZiVLU/lHy+6G14Z 7MKw0JOw3rfQyhIKoohy8BwttX2eV1jaHi54jmuA9ptk97WaZX0YNI9B/k0E1LLS ABIgZDfOFBvsc8rY8WShJW5BGpGqgHVaOOP29Pph7DXYgyPffy0w/QW67p1pt3eC s= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=x8O/Fr 5KKdQsu5P1ynz+Cb29hN5tV5dHnES7Q29hjuM=; b=R2R+HREjbviFeKADJWFVaG zKY4VJ/kPRLTLlpGXY9U9CMAkZz+hRUPG8ewplLzZVh1Ul98v9R18sRN+2yS0QpZ XWpgQkxD2pjbJqSI6KRSaosBo84U6ZuBlRpkXQtiiYT3jI+beoh+EOiT4KyaXijR EzzHUpMMWBs45+RizRfTA81r+szKeYv7BLRiyERvKhEab2CCB1ZTc6PTAdYGva5b nod8Xq0qy2T5Ty6+jzTqeQbvtOqv9Gpg6p2nzKx3N3E8o2mTW9NK9K5EnBglxHwr qr1QpLIt5fjrn2Oi7HMuIvdqzuIRRSqdznVmZoFMyfYTFg3g4/bXM5vb+6Z+HH0g == X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 5D9C4E4314; Tue, 29 May 2018 11:24:44 -0400 (EDT) From: Thomas Monjalon To: Marko Kovacevic Cc: dev@dpdk.org, ferruh.yigit@intel.com, john.mcnamara@intel.com Date: Tue, 29 May 2018 17:24:43 +0200 Message-ID: <6140320.jqdv53SyBi@xps> In-Reply-To: <20180529110124.35666-1-marko.kovacevic@intel.com> References: <20180528152342.22467-1-marko.kovacevic@intel.com> <20180529110124.35666-1-marko.kovacevic@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2] doc: add guides for patch fix issues 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: Tue, 29 May 2018 15:24:45 -0000 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.