mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Oscar Alejandro Sánchez Lucero via B4 Relay"
	<devnull+aleszlucero.gmail.com@kernel.org>,
	"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,
	"Oscar Alejandro Sánchez Lucero" <aleszlucero@gmail.com>
Subject: Re: [PATCH v5] doc: process: clarify scope of applying-patches as legacy reference
Date: Fri, 06 Nov 2026 02:36:21 -0700	[thread overview]
Message-ID: <87cxsi9u96.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20261105-doc-patch-fix-v5-1-0658a9e3e235@gmail.com>

Oscar Alejandro Sánchez Lucero via B4 Relay
<devnull+aleszlucero.gmail.com@kernel.org> writes:

> 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>
> ---
> Update the applying-patches.rst document to clarify that it serves as a
> reference for legacy or constrained workflows where Git infrastructure
> is unavailable, redirecting new contributors to standard Git-based tools.
> ---
> Changes in v5:
> - EDITME: describe what is new in this series revision.
> - EDITME: use bulletpoints and terse descriptions.
> - Link to v4: https://lore.kernel.org/r/20261105-doc-patch-fix-v4-1-3eb49e363f64@gmail.com

Please slow down - two revisions one minute apart really makes no sense
at all.

Thanks,

jon

      reply	other threads:[~2026-11-06  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 19:15 Oscar Alejandro Sánchez Lucero via B4 Relay
2026-11-06  9:36 ` Jonathan Corbet [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=87cxsi9u96.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=aleszlucero@gmail.com \
    --cc=devnull+aleszlucero.gmail.com@kernel.org \
    --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 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®