From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: fix rst issues in testpmd user guide
Date: Fri, 23 Oct 2015 08:36:12 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE20238CC89@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8973C81F0C2@IRSMSX108.ger.corp.intel.com>
> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Thursday, October 1, 2015 5:27 PM
> To: Mcnamara, John; dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH] doc: fix rst issues in testpmd user guide
>
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of John McNamara
> > Sent: Monday, September 28, 2015 8:46 PM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] [PATCH] doc: fix rst issues in testpmd user guide
> >
> > Fix a number of RST issues in the testpmd user guide and refactored
> > the structure to:
> >
> > * Remove redundant roadmap section.
> > * Merge Overview section into Introduction.
> > * Move "set fwd" to the start of its section.
> >
> > Signed-off-by: John McNamara <john.mcnamara@intel.com>
>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Hi,
I know docs are low priority but can we get this one merged since there are other pending software changes to testpmd with flow director and when we add documentation for them it would be better if they were in the updated, clearer, format.
John.
--
next prev parent reply other threads:[~2015-10-23 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 19:45 John McNamara
2015-10-01 16:26 ` De Lara Guarch, Pablo
2015-10-23 8:36 ` Mcnamara, John [this message]
2015-10-26 14:36 ` 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=B27915DBBA3421428155699D51E4CFE20238CC89@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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).