From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jelle van der Waa <jvanderw@redhat.com>,
Thorsten Leemhuis <linux@leemhuis.info>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, James Addison <jay@jp-hosting.net>
Subject: Re: [PATCH v3 1/1] docs: Disambiguate a pair of rST labels
Date: Tue, 8 Apr 2025 07:33:55 +0700 [thread overview]
Message-ID: <Z_Ru84ecc13jE9ZZ@archie.me> (raw)
In-Reply-To: <20250407195120.331103-2-jvanderwaa@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]
[fixing Jelle's submission address]
On Mon, Apr 07, 2025 at 09:51:20PM +0200, JellevanderWaa wrote:
> diff --git a/Documentation/admin-guide/quickly-build-trimmed-linux.rst b/Documentation/admin-guide/quickly-build-trimmed-linux.rst
> index 07cfd8863b46..4a5ffb0996a3 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_improvements_qbtl:
>
> 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_improvements_qbtl>`.
>
>
> ..
> diff --git a/Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst b/Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
> index 03c55151346c..d8946b084b1e 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_improvements_vbbr>`.
>
> .. _introprep_bissbs:
>
> @@ -1055,7 +1055,7 @@ follow these instructions.
>
> [:ref:`details <introoptional_bisref>`]
>
> -.. _submit_improvements:
> +.. _submit_improvements_vbbr:
>
> Conclusion
> ----------
LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
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-04-08 0:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 19:51 [PATCH v3 0/1] reproducible sphinx docs Jelle
2025-04-07 19:51 ` [PATCH v3 1/1] docs: Disambiguate a pair of rST labels Jelle
2025-04-08 0:33 ` Bagas Sanjaya [this message]
2025-04-09 16:21 ` James Addison
2025-04-14 16:27 ` Jonathan Corbet
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=Z_Ru84ecc13jE9ZZ@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@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.