From: James Clark <james.clark@arm.com>
To: nfraprado@protonmail.com, n@nfraprado.net, linux-doc@vger.kernel.org
Cc: mchehab+huawei@kernel.org, corbet@lwn.net,
James Clark <james.clark@arm.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/1] docs: automarkup.py: Fix invalid HTML link output and broken URI fragments
Date: Wed, 5 Jan 2022 14:36:38 +0000 [thread overview]
Message-ID: <20220105143640.330602-1-james.clark@arm.com> (raw)
Changes since v1:
* Re-ordered comments so that they align with the correct code
* Add Nícolas's review tag
James Clark (1):
docs: automarkup.py: Fix invalid HTML link output and broken URI
fragments
Documentation/sphinx/automarkup.py | 25 ++++++++++++++++++-------
1 file changed, 18 insertions(+), 7 deletions(-)
--
2.28.0
next reply other threads:[~2022-01-05 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 14:36 James Clark [this message]
2022-01-05 14:36 ` [PATCH v2 1/1] docs: automarkup.py: Fix invalid HTML link output and broken URI fragments 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
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=20220105143640.330602-1-james.clark@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 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.