From: Randy Dunlap <rdunlap@infradead.org>
To: aleszlucero@gmail.com, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: process: clarify scope of applying-patches as legacy reference
Date: Wed, 4 Nov 2026 10:09:45 -0800 [thread overview]
Message-ID: <706deeb8-8d19-42db-b6fd-cb37195cce0b@infradead.org> (raw)
In-Reply-To: <20261104-doc-patch-fix-v1-1-617cb9f4cd47@gmail.com>
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
prev parent reply other threads:[~2026-11-04 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 13:53 AleSZLucero via B4 Relay
2026-11-04 17:56 ` Krzysztof Kozlowski
2026-11-04 18:09 ` Randy Dunlap [this message]
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=706deeb8-8d19-42db-b6fd-cb37195cce0b@infradead.org \
--to=rdunlap@infradead.org \
--cc=aleszlucero@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®