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>,
	aleszlucero@gmail.com
Cc: rdunlap@infradead.org, krzk@kernel.org, wy@wyuan.org,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: process: clarify legacy status of applying-patches and point to Git
Date: Sat, 07 Nov 2026 00:57:11 -0700	[thread overview]
Message-ID: <871p8x9iqw.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20261106-doc-modernize-git-v1-1-8b59c1a578ba@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 heavily details the legacy 'patch'
> utility, which creates confusion for new contributors since current
> development relies almost entirely on Git infrastructure.
>
> This patch updates the opening notes to explicitly mark the manual
> patching process as a legacy reference and redirects readers to
> contemporary Git-based guides.
>
> Signed-off-by: Oscar Alejandro Sánchez Lucero <aleszlucero@gmail.com>

So how does this relate to the other patch that you sent six times in
quick succession?

> The applying-patches.rst document heavily details the legacy 'patch'
> utility, which creates confusion for new contributors since current
> development relies almost entirely on Git infrastructure.
>
> This series updates the introduction to explicitly mark the manual 
> patching process as a legacy reference and redirects readers to 
> contemporary Git-based guides.

...and why are you repeating this text here?

Thanks,

jon

  reply	other threads:[~2026-11-07  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 21:49 Oscar Alejandro Sánchez Lucero via B4 Relay
2026-11-07  7:57 ` Jonathan Corbet [this message]
2026-11-07  8:10   ` Alejandro Lucero

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=871p8x9iqw.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=aleszlucero@gmail.com \
    --cc=devnull+aleszlucero.gmail.com@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=workflows@vger.kernel.org \
    --cc=wy@wyuan.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®