* [PATCH] docs: submitting-patches: Fix crossref to 'The canonical patch format'
@ 2022-04-27 9:28 Akira Yokosawa
2022-04-28 18:29 ` Jonathan Corbet
0 siblings, 1 reply; 2+ messages in thread
From: Akira Yokosawa @ 2022-04-27 9:28 UTC (permalink / raw)
To: Jonathan Corbet, Mauro Carvalho Chehab
Cc: Akira Yokosawa, linux-doc, linux-kernel
The reference to `explicit_in_reply_to` is pointless as when the
reference was added in the form of "#15" [1], Section 15) was "The
canonical patch format".
The reference of "#15" had not been properly updated in a couple of
reorganizations during the plain-text SubmittingPatches era.
Fix it by using `the_canonical_patch_format`.
[1]: 2ae19acaa50a ("Documentation: Add "how to write a good patch summary" to SubmittingPatches")
Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Fixes: 5903019b2a5e ("Documentation/SubmittingPatches: convert it to ReST markup")
Fixes: 9b2c76777acc ("Documentation/SubmittingPatches: enrich the Sphinx output")
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: stable@vger.kernel.org # v4.9+
---
Documentation/process/submitting-patches.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index 9bb4e8c0f635..bf5ead743ccf 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -77,7 +77,7 @@ as you intend it to.
The maintainer will thank you if you write your patch description in a
form which can be easily pulled into Linux's source code management
-system, ``git``, as a "commit log". See :ref:`explicit_in_reply_to`.
+system, ``git``, as a "commit log". See :ref:`the_canonical_patch_format`.
Solve only one problem per patch. If your description starts to get
long, that's a sign that you probably need to split up your patch.
base-commit: f5461124d59bfb62bd9e231ee64cbaf757343ad5
--
2.25.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] docs: submitting-patches: Fix crossref to 'The canonical patch format'
2022-04-27 9:28 [PATCH] docs: submitting-patches: Fix crossref to 'The canonical patch format' Akira Yokosawa
@ 2022-04-28 18:29 ` Jonathan Corbet
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Corbet @ 2022-04-28 18:29 UTC (permalink / raw)
To: Akira Yokosawa, Mauro Carvalho Chehab
Cc: Akira Yokosawa, linux-doc, linux-kernel
Akira Yokosawa <akiyks@gmail.com> writes:
> The reference to `explicit_in_reply_to` is pointless as when the
> reference was added in the form of "#15" [1], Section 15) was "The
> canonical patch format".
> The reference of "#15" had not been properly updated in a couple of
> reorganizations during the plain-text SubmittingPatches era.
>
> Fix it by using `the_canonical_patch_format`.
>
> [1]: 2ae19acaa50a ("Documentation: Add "how to write a good patch summary" to SubmittingPatches")
>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> Fixes: 5903019b2a5e ("Documentation/SubmittingPatches: convert it to ReST markup")
> Fixes: 9b2c76777acc ("Documentation/SubmittingPatches: enrich the Sphinx output")
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: stable@vger.kernel.org # v4.9+
> ---
> Documentation/process/submitting-patches.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
jon
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-04-28 18:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-04-27 9:28 [PATCH] docs: submitting-patches: Fix crossref to 'The canonical patch format' Akira Yokosawa
2022-04-28 18:29 ` Jonathan Corbet
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox