From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v1] doc: add guides for patch fix issues Date: Tue, 29 May 2018 12:32:53 +0200 Message-ID: <7643300.VTXUEitkYP@xps> References: <20180528152342.22467-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 AED4916E for ; Tue, 29 May 2018 12:32:55 +0200 (CEST) In-Reply-To: <20180528152342.22467-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" 28/05/2018 17:23, Marko Kovacevic: > -`Coverity `_ > -is a tool for static code analysis. > -It is used as a cloud-based service used to scan the DPDK source code, > -and alert developers of any potential defects in the source code. > -When fixing an issue found by Coverity, the patch must contain a Coverity issue ID > -in the body of the commit message. For example:: > + `Coverity `_ > + is a tool for static code analysis. > + It is used as a cloud-based service used to scan the DPDK source code, > + and alert developers of any potential defects in the source code. > + When fixing an issue found by Coverity, the patch must contain a Coverity issue ID > + in the body of the commit message. For example:: Why the indentation is changed?