From: Thomas Monjalon <thomas@monjalon.net>
To: "Kovacevic, Marko" <marko.kovacevic@intel.com>
Cc: David Marchand <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: remove file listings
Date: Thu, 17 Jan 2019 17:08:55 +0100 [thread overview]
Message-ID: <6351986.DbtgIHa0yY@xps> (raw)
In-Reply-To: <6DC05C7C5F25994B81B3F2F214251F660207DD13@IRSMSX104.ger.corp.intel.com>
17/01/2019 16:42, Kovacevic, Marko:
> > > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > > ---
> > > doc/guides/prog_guide/dev_kit_build_system.rst | 43 --------------
> > > doc/guides/prog_guide/source_org.rst | 79 +-------------------------
> > > 2 files changed, 2 insertions(+), 120 deletions(-)
> > >
> > > diff --git a/doc/guides/prog_guide/dev_kit_build_system.rst
> > > b/doc/guides/prog_guide/dev_kit_build_system.rst
> > > index da83a31..855b5da 100644
> > > --- a/doc/guides/prog_guide/dev_kit_build_system.rst
> > > +++ b/doc/guides/prog_guide/dev_kit_build_system.rst
> > > @@ -52,49 +52,6 @@ which is equivalent to:
> > >
>
> I agree with the change and deletion of the sections there,
> But I feel like there still needs to be a clickable reference to each section in the docs.
> So if they want to see the drivers or applications they can still be brought there.
I'm not sure to understand your proposal.
Please could you explain?
next prev parent reply other threads:[~2019-01-17 16:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 9:05 David Marchand
2019-01-17 9:16 ` Thomas Monjalon
2019-01-17 15:42 ` Kovacevic, Marko
2019-01-17 16:08 ` Thomas Monjalon [this message]
2019-01-17 16:53 ` Kovacevic, Marko
2019-01-17 17:01 ` Thomas Monjalon
2019-01-18 9:29 ` Kovacevic, Marko
2019-01-18 9:33 ` Thomas Monjalon
2019-01-18 10:15 ` David Marchand
2019-01-17 14:36 ` Ferruh Yigit
2019-01-18 15:31 ` [dpdk-dev] [PATCH v2] " David Marchand
2019-01-18 15:35 ` Kovacevic, Marko
2019-01-20 12:10 ` 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=6351986.DbtgIHa0yY@xps \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--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).