From: Thomas Monjalon <thomas@monjalon.net>
To: "Varghese, Vipin" <vipin.varghese@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"shreyansh.jain@nxp.com" <shreyansh.jain@nxp.com>,
"Padubidri, Sanjay A" <sanjay.padubidri@intel.com>,
"Patel, Amol" <amol.patel@intel.com>
Subject: Re: [dpdk-dev] [PATCH v7 2/2] doc: add guide for debug and troubleshoot
Date: Mon, 08 Apr 2019 08:45:32 +0200 [thread overview]
Message-ID: <2023912.nZ7ZJuuoIi@xps> (raw)
Message-ID: <20190408064532.nDHcbs_q_hdpztK6mVLl50WBh8LXIBfSdsMAC7IcsNM@z> (raw)
In-Reply-To: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D32ACED@BGSMSX101.gar.corp.intel.com>
08/04/2019 05:18, Varghese, Vipin:
> Hi Thomas and John,
>
> Thanks for the comments and suggestion.
>
> snipped
> > > > +
> > > > + It is difficult to cover all possible issues; in a single attempt.
> > > > + With ``feedback and suggestions from the community, more cases can
> > > > + be
> > > > covered``.
> > >
> > > Do you really mean to `` quote (i.e., fixed width quote) the line above?
> In my humble opinion it will be best to highlight.
>
> >
> > I think the quote signs should be removed.
> Ok
>
> >
> > But it would be nice to have such quote for all the code symbols used in this doc.
> Ok
>
> Would like me to send a v8 or can the v7 be accepted with quotes removed while merge?
No Vipin, you need to add quotes everywhere in the doc for the code symbols.
next prev parent reply other threads:[~2019-04-08 6:45 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 4:56 [dpdk-dev] [PATCH v1] doc: add meson build to contributing guide Vipin Varghese
2018-10-30 10:54 ` Bruce Richardson
2018-10-30 14:13 ` [dpdk-dev] [PATCH v2] " Vipin Varghese
2018-10-30 14:18 ` [dpdk-dev] [PATCH v3] " Vipin Varghese
2018-11-14 14:30 ` Kovacevic, Marko
2018-11-24 18:57 ` Thomas Monjalon
2019-01-10 16:37 ` Varghese, Vipin
2019-01-24 23:05 ` [dpdk-dev] [PATCH v4] doc/patches: " Vipin Varghese
2019-01-28 0:39 ` Thomas Monjalon
2019-01-28 14:27 ` Varghese, Vipin
2019-01-28 14:52 ` Thomas Monjalon
2019-01-28 15:40 ` Varghese, Vipin
2019-01-29 10:10 ` [dpdk-dev] [PATCH v5] " Vipin Varghese
2019-02-12 9:36 ` Thomas Monjalon
2019-02-13 5:38 ` Varghese, Vipin
2019-02-13 5:41 ` [dpdk-dev] [PATCH v6] " Vipin Varghese
2019-02-25 17:12 ` [dpdk-dev] [PATCH v7 0/2] guide to debug and troubleshoot Vipin Varghese
2019-02-25 17:12 ` [dpdk-dev] [PATCH v7 1/2] doc: add svg for debug and troubleshoot guide Vipin Varghese
2019-04-01 14:56 ` Mcnamara, John
2019-04-01 14:56 ` Mcnamara, John
2019-02-25 17:12 ` [dpdk-dev] [PATCH v7 2/2] doc: add guide for debug and troubleshoot Vipin Varghese
2019-04-01 14:56 ` Mcnamara, John
2019-04-01 14:56 ` Mcnamara, John
2019-04-05 8:49 ` Thomas Monjalon
2019-04-05 8:49 ` Thomas Monjalon
2019-04-08 3:18 ` Varghese, Vipin
2019-04-08 3:18 ` Varghese, Vipin
2019-04-08 6:45 ` Thomas Monjalon [this message]
2019-04-08 6:45 ` Thomas Monjalon
2019-04-09 6:33 ` Varghese, Vipin
2019-04-09 6:33 ` Varghese, Vipin
2019-04-09 6:33 ` [dpdk-dev] [PATCH v8 0/2] guide to " Vipin Varghese
2019-04-09 6:33 ` Vipin Varghese
2019-04-09 6:33 ` [dpdk-dev] [PATCH v8 1/2] doc: add svg for debug and troubleshoot guide Vipin Varghese
2019-04-09 6:33 ` Vipin Varghese
2019-04-09 6:33 ` [dpdk-dev] [PATCH v8 2/2] doc: add guide for debug and troubleshoot Vipin Varghese
2019-04-09 6:33 ` Vipin Varghese
2019-05-04 22:26 ` [dpdk-dev] [PATCH v8 0/2] guide to " Thomas Monjalon
2019-05-04 22:26 ` Thomas Monjalon
2019-04-01 4:08 ` [dpdk-dev] [PATCH v7 " Varghese, Vipin
2019-04-01 4:08 ` Varghese, Vipin
2019-02-27 11:41 ` [dpdk-dev] [PATCH v6] doc/patches: add meson build to contributing guide Thomas Monjalon
2019-02-27 12:13 ` Varghese, Vipin
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=2023912.nZ7ZJuuoIi@xps \
--to=thomas@monjalon.net \
--cc=amol.patel@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=sanjay.padubidri@intel.com \
--cc=shreyansh.jain@nxp.com \
--cc=vipin.varghese@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).