From: Markus Heiser <markus.heiser@darmarit.de>
To: Jonathan Corbet <corbet@lwn.net>,
Jani Nikula <jani.nikula@linux.intel.com>
Cc: "Tobin C. Harding" <me@tobin.cc>, linux-doc@vger.kernel.org
Subject: Re: undefined label
Date: Tue, 12 Mar 2019 09:19:01 +0100 [thread overview]
Message-ID: <9ed8cf1e-627b-bf04-02ba-26684198c55b@darmarit.de> (raw)
In-Reply-To: <20190311113015.166262c9@lwn.net>
Am 11.03.19 um 18:30 schrieb Jonathan Corbet:
> 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.
>
> jon
>
I know about this, thats why I mentioned this as a drawback.
May I find a soulution which uses intersphinx only when needed
(when using SPHINXDIRS). Anyway it will be only a **RFC**.
But right now I don't have time anyway. ;)
-- Markus --
prev parent reply other threads:[~2019-03-12 8:19 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
2019-03-12 8:19 ` Markus Heiser [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=9ed8cf1e-627b-bf04-02ba-26684198c55b@darmarit.de \
--to=markus.heiser@darmarit.de \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--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 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.