From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jelle van der Waa <jvanderw@redhat.com>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: James Addison <jay@jp-hosting.net>,
Thorsten Leemhuis <linux@leemhuis.info>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [v2 1/1] docs: Disambiguate a pair of rST labels
Date: Thu, 27 Feb 2025 15:13:31 +0700 [thread overview]
Message-ID: <Z8Aeqxnpznvvt_LM@archie.me> (raw)
In-Reply-To: <20250226203516.334067-2-jvanderw@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3813 bytes --]
[Cc'ing Thorsten and Jon]
On Wed, Feb 26, 2025 at 09:34:51PM +0100, Jelle van der Waa wrote:
> From: James Addison <jay@jp-hosting.net>
>
> According to the reStructuredText documentation, internal hyperlink
> targets[1] are intended to resolve within the current document.
>
> Sphinx has a bug that causes internal hyperlinks declared with
> duplicate names to resolve nondeterministically, producing incorrect
> documentation. Sphinx does not yet emit a warning when these
> duplicate target names are declared.
>
> To improve the reproducibility and correctness of the HTML
> documentation, disambiguate two labels both previously titled
> "submit_improvements".
On docs.kernel.org, I click "described above" link on quickly build kernel
guide [1] which takes me to bisection guide instead [2]. Now with this
patch, the same link now points to suggestions and improvements on the
same page.
[1]: https://docs.kernel.org/admin-guide/quickly-build-trimmed-linux.html
[2]: https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html#submit-improvements
>
> [1] - https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#hyperlink-targets
>
> Link: https://github.com/sphinx-doc/sphinx/issues/13383
> Signed-off-by: James Addison <jay@jp-hosting.net>
>
> ---
> V1 -> V2: re-send using different email client
> ---
> Documentation/admin-guide/quickly-build-trimmed-linux.rst | 4 ++--
> .../admin-guide/verify-bugs-and-bisect-regressions.rst | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/admin-guide/quickly-build-trimmed-linux.rst b/Documentation/admin-guide/quickly-build-trimmed-linux.rst
> index 07cfd8863b46..2d1b6f7504c1 100644
> --- a/Documentation/admin-guide/quickly-build-trimmed-linux.rst
> +++ b/Documentation/admin-guide/quickly-build-trimmed-linux.rst
> @@ -347,7 +347,7 @@ again.
>
> [:ref:`details<uninstall>`]
>
> -.. _submit_improvements:
> +.. _submit_trimmed_build_improvements:
>
> Did you run into trouble following any of the above steps that is not cleared up
> by the reference section below? Or do you have ideas how to improve the text?
> @@ -1070,7 +1070,7 @@ complicated, and harder to follow.
>
> That being said: this of course is a balancing act. Hence, if you think an
> additional use-case is worth describing, suggest it to the maintainers of this
> -document, as :ref:`described above <submit_improvements>`.
> +document, as :ref:`described above <submit_trimmed_build_improvements>`.
>
>
> ..
> diff --git a/Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst b/Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
> index 03c55151346c..1b246d8a8afb 100644
> --- a/Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
> +++ b/Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
> @@ -267,7 +267,7 @@ culprit might be known already. For further details on what actually qualifies
> as a regression check out Documentation/admin-guide/reporting-regressions.rst.
>
> If you run into any problems while following this guide or have ideas how to
> -improve it, :ref:`please let the kernel developers know <submit_improvements>`.
> +improve it, :ref:`please let the kernel developers know <submit_regression_tracing_improvements>`.
>
> .. _introprep_bissbs:
>
> @@ -1055,7 +1055,7 @@ follow these instructions.
>
> [:ref:`details <introoptional_bisref>`]
>
> -.. _submit_improvements:
> +.. _submit_regression_tracing_improvements:
>
> Conclusion
> ----------
The patch itself looks good.
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-02-27 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 22:59 [PATCH] docs: Disambiguate a pair of rST labels James Addison
2025-02-24 0:43 ` Bagas Sanjaya
2025-02-26 20:34 ` [v2 0/1] reproducible sphinx docs Jelle van der Waa
2025-02-27 8:05 ` Bagas Sanjaya
2025-02-26 20:34 ` [v2 1/1] docs: Disambiguate a pair of rST labels Jelle van der Waa
2025-02-27 8:13 ` Bagas Sanjaya [this message]
2025-02-27 10:17 ` Thorsten Leemhuis
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=Z8Aeqxnpznvvt_LM@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=jay@jp-hosting.net \
--cc=jvanderw@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
/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.