From: Jonathan Corbet <corbet@lwn.net>
To: "Nícolas F. R. A. Prado" <nfraprado@protonmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, lkcamp@lists.libreplanetbr.org,
andrealmeid@collabora.com
Subject: Re: [PATCH] docs: dt: Use full path to enable cross-reference
Date: Mon, 30 Nov 2020 14:24:04 -0700 [thread overview]
Message-ID: <20201130142404.6ef6689e@lwn.net> (raw)
In-Reply-To: <20201123121333.59274-1-nfraprado@protonmail.com>
On Mon, 23 Nov 2020 12:13:46 +0000
Nícolas F. R. A. Prado <nfraprado@protonmail.com> wrote:
> Use full path to reference writing-schema.rst so that it becomes a
> cross-reference.
>
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@protonmail.com>
> ---
>
> Hi Jon,
>
> do you think this would be the way to go, or should we instead extend automarkup
> to work on relative paths to doc pages, so that this reference would work as is?
Sorry, I missed this before ... dunno. I suppose that recognizing
relative paths would be a friendly gesture toward our documentation
writers and might be worth doing.
Either way, it occurs to me that automarkup should check to see whether
the file actually exists and complain if it doesn't.
For now, I'll apply this one, though.
Thanks,
jon
prev parent reply other threads:[~2020-11-30 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 12:13 [PATCH] docs: dt: Use full path to enable cross-reference Nícolas F. R. A. Prado
2020-11-30 21:24 ` Jonathan Corbet [this message]
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=20201130142404.6ef6689e@lwn.net \
--to=corbet@lwn.net \
--cc=andrealmeid@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=mchehab+huawei@kernel.org \
--cc=nfraprado@protonmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).