From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Markus Heiser <markus.heiser@darmarit.de>,
"Tobin C. Harding" <me@tobin.cc>,
linux-doc@vger.kernel.org
Subject: Re: undefined label
Date: Tue, 12 Mar 2019 09:57:30 +0200 [thread overview]
Message-ID: <874l88frth.fsf@intel.com> (raw)
In-Reply-To: <20190311113015.166262c9@lwn.net>
On Mon, 11 Mar 2019, Jonathan Corbet <corbet@lwn.net> wrote:
> On Fri, 08 Mar 2019 14:17:47 +0200
> Jani Nikula <jani.nikula@linux.intel.com> wrote:
>
>> > >> To close such cross-books links we can use intersphinx [1] and map to e.g.
>> > >>
>> > >> intersphinx_mapping = {
>> > >> 'kernel': ('https://www.kernel.org/doc/html/latest/', None)}
>> >
>> > This requires online access while building the output. Anyway, as soon as
>> > I have some time to spare I will send a RFC with more explanation about
>> > (you will receive it in CC).
>>
>> Please remember to call out the online access in the patch series. Such
>> a requirement is going to draw a lot of opposition.
>
> Indeed, I think that would a difficult requirement to add. It may well be
> better, in the end, to simply document this "feature" and live with it.
Apparently it's also possible to have a local intersphinx mapping file
which could be committed to git [1]. That obviously needs to be manually
updated occasionally, which is a bit tedious.
IIUC intersphinx also means that if a cross-reference target is not
present in the documentation being built, it'll use the canonical URL in
the intersphinx_mapping. So your locally built documentation for a
sub-book might contain links to kernel.org. I'm not sure whether that's
better or worse than broken links.
BR,
Jani.
[1] https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html#confval-intersphinx_mapping
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2019-03-12 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 9:17 undefined label Tobin C. Harding
2019-03-07 9:58 ` Markus Heiser
2019-03-07 20:30 ` Tobin C. Harding
2019-03-08 8:56 ` Markus Heiser
2019-03-08 12:17 ` Jani Nikula
2019-03-11 17:30 ` Jonathan Corbet
2019-03-12 7:57 ` Jani Nikula [this message]
2019-03-12 8:19 ` Markus Heiser
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=874l88frth.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=me@tobin.cc \
/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).