From: James Clark <james.clark@arm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: mchehab+huawei@kernel.org, linux-kernel@vger.kernel.org,
nfraprado@protonmail.com, n@nfraprado.net,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 1/1] docs: automarkup.py: Fix invalid HTML link output and broken URI fragments
Date: Fri, 7 Jan 2022 10:04:44 +0000 [thread overview]
Message-ID: <0fce859e-4ac5-3e41-a4cf-ec1c22f2c3cc@arm.com> (raw)
In-Reply-To: <87h7agpkn4.fsf@meer.lwn.net>
On 06/01/2022 22:25, Jonathan Corbet wrote:
> James Clark <james.clark@arm.com> writes:
>
>> Since commit d18b01789ae5 ("docs: Add automatic cross-reference for
>> documentation pages"), references that were already explicitly defined
>> with "ref:" and referred to other pages with a path have been doubled.
>> This is reported as the following error by Firefox:
> [...]
>> The fix is to check that nodes in the document to be modified are not
>> already references. A reference is counted as any text that is a
>> descendant of a reference type node. Only plain text should be converted
>> to new references, otherwise the doubling occurs.
>
> This seems like a good fix. Applied, thanks.
>
> jon
>
Thanks Jonathan. Do you have a git repo that these get applied to?
I wasn't able to find it on https://git.kernel.org/
next prev parent reply other threads:[~2022-01-07 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 14:36 [PATCH v2 0/1] docs: automarkup.py: Fix invalid HTML link output and broken URI fragments James Clark
2022-01-05 14:36 ` [PATCH v2 1/1] " James Clark
2022-01-06 22:25 ` Jonathan Corbet
2022-01-07 10:04 ` James Clark [this message]
2022-01-07 16:33 ` Nícolas F. R. A. Prado
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=0fce859e-4ac5-3e41-a4cf-ec1c22f2c3cc@arm.com \
--to=james.clark@arm.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=n@nfraprado.net \
--cc=nfraprado@protonmail.com \
/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