From: Thomas Monjalon <thomas@monjalon.net>
To: Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v1] doc: add guides for patch fix issues
Date: Tue, 29 May 2018 12:32:53 +0200 [thread overview]
Message-ID: <7643300.VTXUEitkYP@xps> (raw)
In-Reply-To: <20180528152342.22467-1-marko.kovacevic@intel.com>
28/05/2018 17:23, Marko Kovacevic:
> -`Coverity <https://scan.coverity.com/projects/dpdk-data-plane-development-kit>`_
> -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 <https://scan.coverity.com/projects/dpdk-data-plane-development-kit>`_
> + 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?
next prev parent reply other threads:[~2018-05-29 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 15:23 Marko Kovacevic
2018-05-28 15:53 ` Ferruh Yigit
2018-05-29 10:32 ` Thomas Monjalon [this message]
2018-05-29 10:45 ` Kovacevic, Marko
2018-05-29 11:01 ` [dpdk-dev] [PATCH v2] " Marko Kovacevic
2018-05-29 15:24 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7643300.VTXUEitkYP@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).