From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Baruch Siach <baruch@tkos.co.il>,
John McNamara <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 1/3] doc: note that the app list is incomplete
Date: Thu, 09 Feb 2017 15:49:04 +0100 [thread overview]
Message-ID: <2246926.L6kT7PA4fr@xps13> (raw)
In-Reply-To: <1986059.8qxn6Y6BpT@xps13>
2016-12-06 17:53, Thomas Monjalon:
> 2016-12-06 14:38, Baruch Siach:
> > Extend the note at the end of Source Organization chapter to also mention
> > the app directory.
> >
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> [...]
> > --- a/doc/guides/prog_guide/source_org.rst
> > +++ b/doc/guides/prog_guide/source_org.rst
> > @@ -162,5 +162,5 @@ The examples directory contains sample applications that show how libraries can
> >
> > .. note::
> >
> > - The actual examples directory may contain additional sample applications to those shown above.
> > + The actual app and examples directories may contain additional applications to those shown above.
> > Check the latest DPDK source files for details.
>
> I suggest to remove this file.
> Each libraries, drivers and applications are documented somewhere else.
> We really must avoid repeating ourself in the documentation and keep
> a reasonnably maintainable documentation.
Any comment?
prev parent reply other threads:[~2017-02-09 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 12:38 Baruch Siach
2016-12-06 12:38 ` [dpdk-dev] [PATCH v2 2/3] doc: correct the description of the app directory Baruch Siach
2016-12-06 12:48 ` Mcnamara, John
2016-12-06 12:38 ` [dpdk-dev] [PATCH v2 3/3] doc: consistently quote directory names Baruch Siach
2016-12-06 12:48 ` Mcnamara, John
2016-12-06 12:48 ` [dpdk-dev] [PATCH v2 1/3] doc: note that the app list is incomplete Mcnamara, John
2016-12-06 16:53 ` Thomas Monjalon
2017-02-09 14:49 ` Thomas Monjalon [this message]
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=2246926.L6kT7PA4fr@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=baruch@tkos.co.il \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).