From: Thomas Monjalon <thomas@monjalon.net>
To: Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, john.mcnamara@intel.com,
Herakliusz Lipiec <herakliusz.lipiec@intel.com>
Subject: Re: [dpdk-dev] [PATCH v9 1/2] doc: add generic compilation doc for all sample apps
Date: Wed, 25 Oct 2017 12:26:40 +0200 [thread overview]
Message-ID: <1666015.7Vdc7jZGnZ@xps> (raw)
In-Reply-To: <1508415063-233624-1-git-send-email-marko.kovacevic@intel.com>
19/10/2017 14:11, Marko Kovacevic:
> +.. _sample_app_compilation:
> +
> +Compiling the Sample Applications
> +=================================
I think we should stop adding useless anchors.
I may be wrong but I don't see the benefit of
:ref:`sample_app_compilation`
compared to
:doc:`compiling`
next prev parent reply other threads:[~2017-10-25 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 12:11 Marko Kovacevic
2017-10-19 12:11 ` [dpdk-dev] [PATCH v9 2/2] doc: add new introduction to sample app guides Marko Kovacevic
2017-10-20 10:32 ` Mcnamara, John
2017-10-20 10:31 ` [dpdk-dev] [PATCH v9 1/2] doc: add generic compilation doc for all sample apps Mcnamara, John
2017-10-25 10:26 ` Thomas Monjalon [this message]
2017-10-25 14:32 ` Mcnamara, John
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=1666015.7Vdc7jZGnZ@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=herakliusz.lipiec@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).