DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Kovacevic, Marko" <marko.kovacevic@intel.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: Fri, 18 Jan 2019 11:15:04 +0100	[thread overview]
Message-ID: <CAJFAV8ybkUJHd6L-LyX2MVcK98h=eS5FazDQNZnP4yvj4fJO+g@mail.gmail.com> (raw)
In-Reply-To: <1905401.XaQ9rUAKQu@xps>

On Fri, Jan 18, 2019 at 10:33 AM Thomas Monjalon <thomas@monjalon.net>
wrote:

> 18/01/2019 10:29, Kovacevic, Marko:
> > > > Sorry for not making it clearer,
> > > > So if someone was reading it and saw this line
> > > >
> > > > "The examples directory contains sample applications that show how
> > > libraries can be used"
> > > >
> > > > It would be nice to have a link to the sample applications in the
> docs
> > > > like so, which has all the Info that was deleted.
> > > >
> > > > "The examples directory contains :doc: ../sample_app_ug/index> that
> show how libraries can be
> > > used."
> > > >
>
> Yes, good idea.
>

Ok, I will prepare a v2 with this.

-- 
David Marchand

  reply	other threads:[~2019-01-18 10:15 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
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 [this message]
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='CAJFAV8ybkUJHd6L-LyX2MVcK98h=eS5FazDQNZnP4yvj4fJO+g@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@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).