All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Marko Kovacevic <marko.kovacevic@intel.com>, john.mcnamara@intel.com
Cc: dev@dpdk.org
Subject: Re: [PATCH v6 2/2] doc: add new introduction to sample app guides
Date: Sat, 14 Oct 2017 00:17:12 +0200	[thread overview]
Message-ID: <4114541.7HO4y25um2@xps> (raw)
In-Reply-To: <1507737087-138205-2-git-send-email-marko.kovacevic@intel.com>

Hi,

11/10/2017 17:51, Marko Kovacevic:
> --- a/doc/guides/sample_app_ug/ipsec_secgw.rst
> +++ b/doc/guides/sample_app_ug/ipsec_secgw.rst
> @@ -28,6 +28,8 @@
>      (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
>      OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>  
> +.. _sample_app_ipsec_secgw:
> +
>  IPsec Security Gateway Sample Application
>  =========================================
>  
> diff --git a/doc/guides/sample_app_ug/l2_forward_real_virtual.rst b/doc/guides/sample_app_ug/l2_forward_real_virtual.rst
> index ba64ea2..901603e 100644
> --- a/doc/guides/sample_app_ug/l2_forward_real_virtual.rst
> +++ b/doc/guides/sample_app_ug/l2_forward_real_virtual.rst
> @@ -28,7 +28,7 @@
>      (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
>      OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>  
> -.. _l2_fwd_app_real_and_virtual:
> +.. _sample_app_l2_fwd:
>  
>  L2 Forwarding Sample Application (in Real and Virtualized Environments)
>  =======================================================================

You don't need to add such anchor at the top of a doc.
You can refer to a doc with :doc: tag.
Please do not add more useless anchors.

Idea for another patch: remove all useless anchors at top of files :)

  parent reply	other threads:[~2017-10-13 22:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05 11:12 [PATCH v4 1/2] doc: add generic compilation doc for all sample apps Marko Kovacevic
2017-10-05 11:12 ` [PATCH v4 2/2] doc: add new introduction to sample app guides Marko Kovacevic
2017-10-05 17:48   ` Mcnamara, John
2017-10-05 17:26 ` [PATCH v4 1/2] doc: add generic compilation doc for all sample apps Mcnamara, John
2017-10-09 16:19 ` [PATCH v5 " Marko Kovacevic
2017-10-09 16:19   ` [PATCH v5 2/2] doc: add new introduction to sample app guides Marko Kovacevic
2017-10-09 16:50     ` Mcnamara, John
2017-10-09 16:48   ` [PATCH v5 1/2] doc: add generic compilation doc for all sample apps Mcnamara, John
2017-10-11 15:51   ` [PATCH v6 " Marko Kovacevic
2017-10-11 15:51     ` [PATCH v6 2/2] doc: add new introduction to sample app guides Marko Kovacevic
2017-10-12 10:55       ` Mcnamara, John
2017-10-13 22:17       ` Thomas Monjalon [this message]
2017-10-16 14:50       ` [PATCH v7 1/2] doc: add generic compilation doc for all sample apps Marko Kovacevic
2017-10-16 14:50         ` [PATCH v7 2/2] doc: add new introduction to sample app guides Marko Kovacevic
2017-10-16 18:53           ` Mcnamara, John
2017-10-18  9:28           ` [PATCH v8 1/2] doc: add generic compilation doc for all sample apps Marko Kovacevic
2017-10-18  9:28             ` [PATCH v8 2/2] doc: add new introduction to sample app guides Marko Kovacevic
2017-10-12 10:55     ` [PATCH v6 1/2] doc: add generic compilation doc for all sample apps 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=4114541.7HO4y25um2@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.