From: Matthew Wilcox <willy@infradead.org>
To: Federico Vaga <federico.vaga@vaga.pv.it>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] doc:process: add links where missing
Date: Wed, 21 Nov 2018 05:23:46 -0800 [thread overview]
Message-ID: <20181121132346.GG3065@bombadil.infradead.org> (raw)
In-Reply-To: <20181121003519.12559-1-federico.vaga@vaga.pv.it>
On Wed, Nov 21, 2018 at 01:35:19AM +0100, Federico Vaga wrote:
> Some documents are refering to others without links. With this
> patch I add those missing links.
I am a neophyte to ReST, but ...
> +++ b/Documentation/dev-tools/coccinelle.rst
> @@ -4,6 +4,8 @@
>
> .. highlight:: none
>
> +.. _devtools_coccinelle:
> +
> Coccinelle
> ==========
>
> +++ b/Documentation/process/4.Coding.rst
> @@ -315,7 +315,8 @@ variety of potential coding problems; it can also propose fixes for those
> problems. Quite a few "semantic patches" for the kernel have been packaged
> under the scripts/coccinelle directory; running "make coccicheck" will run
> through those semantic patches and report on any problems found. See
> -Documentation/dev-tools/coccinelle.rst for more information.
> +:ref:`Documentation/dev-tools/coccinelle.rst <devtools_coccinelle>`
> +for more information.
when I tried to do something like this yesterday, I discovered that
doing:
+.. _memory_allocation:
didn't work, and I had to do:
+.. _memory-allocation:
instead. Also, when doing 'ref', do we want this style of ref, or do we
prefer the plain:
:ref:`devtools-coccinelle`
which is what I did yesterday. Maybe that's why yours works with the
underscores and mine didn't?
next prev parent reply other threads:[~2018-11-21 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 0:35 Federico Vaga
2018-11-21 13:23 ` Matthew Wilcox [this message]
2018-11-21 15:53 ` Federico Vaga
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=20181121132346.GG3065@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®