From: "Kovacevic, Marko" <marko.kovacevic@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] doc: add guides for patch fix issues
Date: Tue, 29 May 2018 10:45:57 +0000 [thread overview]
Message-ID: <6DC05C7C5F25994B81B3F2F214251F6601FE835F@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <7643300.VTXUEitkYP@xps>
> 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?
>
My bad I tried doing it differently yesterday and saw the way you changed it
And just kept it the same way because it looked good but forgot to bring the text back.
I'll send a v2 now.
Marko K
next prev parent reply other threads:[~2018-05-29 10:46 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
2018-05-29 10:45 ` Kovacevic, Marko [this message]
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=6DC05C7C5F25994B81B3F2F214251F6601FE835F@IRSMSX104.ger.corp.intel.com \
--to=marko.kovacevic@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
/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).