From: Krzysztof Kozlowski <krzk@kernel.org>
To: aleszlucero@gmail.com, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] doc: process: clarify scope of applying-patches as legacy reference
Date: Thu, 5 Nov 2026 09:28:54 +0100 [thread overview]
Message-ID: <832e8281-4e9f-43c2-9477-9f5a5a666d41@kernel.org> (raw)
In-Reply-To: <20261104-doc-patch-fix-v3-1-f71cc8ded7d9@gmail.com>
On 04/11/2026 19:31, Oscar Alejandro Sánchez Lucero via B4 Relay wrote:
> From: Oscar Alejandro Sánchez Lucero <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 a direct
> cross-reference to howto.rst to steer contributors toward the standard
> Git infrastructure.
>
> Signed-off-by: Oscar Alejandro Sánchez Lucero <aleszlucero@gmail.com>
> ---
> Signed-off-by: AleSZLucero <aleszlucero@gmail.com>
Drop
> ---
> Changes in v3:
> - EDITME: describe what is new in this series revision.
> - EDITME: use bulletpoints and terse descriptions.
> - Link to v2: https://lore.kernel.org/r/20261104-doc-patch-fix-v2-1-3601fc35c505@gmail.com
>
> Changes in v2:
> - EDITME: describe what is new in this series revision.
> - EDITME: use bulletpoints and terse descriptions.
> - Link to v1: https://lore.kernel.org/r/20261104-doc-patch-fix-v1-1-617cb9f4cd47@gmail.com
Do you see EDITME?
> ---
> Documentation/process/applying-patches.rst | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
...
> 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
> @@ -20,7 +26,6 @@ In addition to explaining how to apply and revert patches, a brief
> description of the different kernel trees (and examples of how to apply
> their specific patches) is also provided.
>
> -
Why?
Best regards,
Krzysztof
prev parent reply other threads:[~2026-11-05 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 18:31 [PATCH v3] doc: process: clarify scope of applying-patches as legacy reference Oscar Alejandro Sánchez Lucero via B4 Relay
2026-11-04 18:31 ` Oscar Alejandro Sánchez Lucero
2026-11-05 8:14 ` Weijie Yuan
2026-11-05 8:28 ` Krzysztof Kozlowski [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=832e8281-4e9f-43c2-9477-9f5a5a666d41@kernel.org \
--to=krzk@kernel.org \
--cc=aleszlucero@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 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.