[PATCH] doc: process: clarify scope of applying-patches as legacy reference

[PATCH] doc: process: clarify scope of applying-patches as legacy reference

[AleSZLucero via B4 Relay]

From: AleSZLucero <aleszlucero@gmail.com>

The applying-patches.rst document describes the manual manipulation of
source trees using the traditional 'patch' and 'diff' utilities. While
technically accurate for non-Git or constrained environments, it can
create friction for new contributors seeking the primary Git-based
workflows.

Update the opening note to explicitly state that this document serves
as a reference for legacy or constrained workflows. Provide direct
cross-references to submitting-patches.rst and howto.rst to steer
contributors toward the standard Git infrastructure.

Signed-off-by: AleSZLucero <aleszlucero@gmail.com>
---
 Documentation/process/applying-patches.rst | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/Documentation/process/applying-patches.rst b/Documentation/process/applying-patches.rst
index c269f5e1a0a3..74af6d8a2249 100644
--- a/Documentation/process/applying-patches.rst
+++ b/Documentation/process/applying-patches.rst
@@ -8,8 +8,15 @@ Original by:
 
 .. note::
 
-   This document is obsolete.  In most cases, rather than using ``patch``
-   manually, you'll almost certainly want to look at using Git instead.
+   This document focuses on the legacy method of manually manipulating source
+   trees using the traditional ``patch`` and ``diff`` utilities.
+
+   For the standard Git-based workflow used in current development, including
+   how to format, apply, and send patches via Git, please refer to
+   :ref:`submitting_patches` and :ref:`howto`.
+
+   The information below is maintained as a reference for constrained
+   environments or legacy workflows where Git infrastructure is unavailable.
 
 A frequently asked question on the Linux Kernel Mailing List is how to apply
 a patch to the kernel or, more specifically, what base kernel a patch for

---
base-commit: 05441d697f7f9a927264f4058cbbc6a03dfcac9d
change-id: 20261104-doc-patch-fix-0241ebee9254

Best regards,
-- 
AleSZLucero <aleszlucero@gmail.com>

Re: [PATCH] doc: process: clarify scope of applying-patches as legacy reference

[Krzysztof Kozlowski]

On 04/11/2026 14:53, AleSZLucero via B4 Relay wrote:
> From: AleSZLucero <aleszlucero@gmail.com>
> 
> The applying-patches.rst document describes the manual manipulation of
> source trees using the traditional 'patch' and 'diff' utilities. While
> technically accurate for non-Git or constrained environments, it can
> create friction for new contributors seeking the primary Git-based
> workflows.
> 
> Update the opening note to explicitly state that this document serves
> as a reference for legacy or constrained workflows. Provide direct
> cross-references to submitting-patches.rst and howto.rst to steer
> contributors toward the standard Git infrastructure.
> 
> Signed-off-by: AleSZLucero <aleszlucero@gmail.com>


Please use known identity (see submitting patches).

> ---
>  Documentation/process/applying-patches.rst | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/process/applying-patches.rst b/Documentation/process/applying-patches.rst
> index c269f5e1a0a3..74af6d8a2249 100644
> --- a/Documentation/process/applying-patches.rst
> +++ b/Documentation/process/applying-patches.rst
> @@ -8,8 +8,15 @@ Original by:
>  
>  .. note::
>  
> -   This document is obsolete.  In most cases, rather than using ``patch``
> -   manually, you'll almost certainly want to look at using Git instead.
> +   This document focuses on the legacy method of manually manipulating source
> +   trees using the traditional ``patch`` and ``diff`` utilities.
> +
> +   For the standard Git-based workflow used in current development, including
> +   how to format, apply, and send patches via Git, please refer to
> +   :ref:`submitting_patches` and :ref:`howto`.

Submitting patches does not provide information on applying patches,
only about sending, right?

This document does not cover sending, therefore I see no point in
providing the reference. I guess howto has something more applicable?


Best regards,
Krzysztof

Re: [PATCH] doc: process: clarify scope of applying-patches as legacy reference

[Randy Dunlap]

On 11/4/26 5:53 AM, AleSZLucero via B4 Relay wrote:
> From: AleSZLucero <aleszlucero@gmail.com>
> 
> The applying-patches.rst document describes the manual manipulation of
> source trees using the traditional 'patch' and 'diff' utilities. While
> technically accurate for non-Git or constrained environments, it can
> create friction for new contributors seeking the primary Git-based
> workflows.
> 
> Update the opening note to explicitly state that this document serves
> as a reference for legacy or constrained workflows. Provide direct
> cross-references to submitting-patches.rst and howto.rst to steer
> contributors toward the standard Git infrastructure.
> 
> Signed-off-by: AleSZLucero <aleszlucero@gmail.com>
> ---
>  Documentation/process/applying-patches.rst | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/process/applying-patches.rst b/Documentation/process/applying-patches.rst
> index c269f5e1a0a3..74af6d8a2249 100644
> --- a/Documentation/process/applying-patches.rst
> +++ b/Documentation/process/applying-patches.rst
> @@ -8,8 +8,15 @@ Original by:
>  
>  .. note::
>  
> -   This document is obsolete.  In most cases, rather than using ``patch``
> -   manually, you'll almost certainly want to look at using Git instead.
> +   This document focuses on the legacy method of manually manipulating source
> +   trees using the traditional ``patch`` and ``diff`` utilities.
> +
> +   For the standard Git-based workflow used in current development, including
> +   how to format, apply, and send patches via Git, please refer to
> +   :ref:`submitting_patches` and :ref:`howto`.
> +
> +   The information below is maintained as a reference for constrained
> +   environments or legacy workflows where Git infrastructure is unavailable.
>  
>  A frequently asked question on the Linux Kernel Mailing List is how to apply
>  a patch to the kernel or, more specifically, what base kernel a patch for

Please test your patches:

Documentation/process/applying-patches.rst:14: WARNING: undefined label: 'submitting_patches' [ref.ref]
Documentation/process/applying-patches.rst:14: WARNING: undefined label: 'howto' [ref.ref]

Additionally, instead of using :ref:s like that, just use the file name
and our automarkup will DTRT (do the right thing) with it.

-- 
~Randy