Linux Documentation
 help / color / mirror / Atom feed
From: "Nícolas F. R. A. Prado" <n@nfraprado.net>
To: James Clark <james.clark@arm.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	mchehab+huawei@kernel.org, linux-kernel@vger.kernel.org,
	nfraprado@protonmail.com, 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 11:33:27 -0500	[thread overview]
Message-ID: <20220107163327.hf26hfinbhhyike3@notapiano> (raw)
In-Reply-To: <0fce859e-4ac5-3e41-a4cf-ec1c22f2c3cc@arm.com>

On Fri, Jan 07, 2022 at 10:04:44AM +0000, James Clark wrote:
> 
> 
> 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/

Yeah, it's not listed there. His tree lives at git://git.lwn.net/linux . I can
see your patch in the docs-next branch.

      reply	other threads:[~2022-01-07 16:33 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
2022-01-07 16:33       ` Nícolas F. R. A. Prado [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=20220107163327.hf26hfinbhhyike3@notapiano \
    --to=n@nfraprado.net \
    --cc=corbet@lwn.net \
    --cc=james.clark@arm.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --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