From: Jani Nikula <jani.nikula@linux.intel.com>
To: Markus Heiser <markus.heiser@darmarit.de>,
"Tobin C. Harding" <me@tobin.cc>
Cc: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Subject: Re: undefined label
Date: Fri, 08 Mar 2019 14:17:47 +0200 [thread overview]
Message-ID: <878sxp7e6s.fsf@intel.com> (raw)
In-Reply-To: <f0891518-ae90-904b-1001-477c122f1abb@darmarit.de>
On Fri, 08 Mar 2019, Markus Heiser <markus.heiser@darmarit.de> wrote:
> Hi Tobin,
>
> Am 07.03.19 um 21:30 schrieb Tobin C. Harding:
>> On Thu, Mar 07, 2019 at 10:58:07AM +0100, Markus Heiser wrote:
> [...]
>>> If there is any interest in, I can implement a RFC for this.
>>
>> Cool! I think this would be super useful, I for one like using
>> SPHINXDIRS when developing docs incrementally so removing false warnings
>> would be nice. I doubt I'm the only one to be baffled about Sphinx
>> references. I'd be happy to review and test your RFC if you CC me.
>
> Intersphinx has also drawbacks. E.g.:
>
> >> 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.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2019-03-08 12:17 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 [this message]
2019-03-11 17:30 ` Jonathan Corbet
2019-03-12 7:57 ` Jani Nikula
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=878sxp7e6s.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).