From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>, linux-doc@vger.kernel.org
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
SeongJae Park <sjpark@amazon.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: describe how to apply incremental stable patches
Date: Wed, 09 Mar 2022 16:29:28 -0700 [thread overview]
Message-ID: <87mthy7lif.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220307063340.256671-1-bagasdotme@gmail.com>
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> The applying patches document
> (Documentation/process/applying-patches.rst) mentions incremental stable
> patches, but there is no example of how to apply them. Describe the
> process.
>
> While at it, remove note about incremental patches and move the external
> link of 5.x.y incremental patches to "Where can I download patches?"
> section.
>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: SeongJae Park <sjpark@amazon.de>
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> Documentation/process/applying-patches.rst | 28 ++++++++++++++++++----
> 1 file changed, 23 insertions(+), 5 deletions(-)
I've applied this, thanks. I do have to wonder, though, how useful this
information is anymore. Does anybody actually apply kernel-patch files
this far into the Git era?
Thanks,
jon
next prev parent reply other threads:[~2022-03-09 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 6:33 [PATCH] Documentation: describe how to apply incremental stable patches Bagas Sanjaya
2022-03-09 23:29 ` Jonathan Corbet [this message]
2022-03-10 0:29 ` Ken Moffat
2022-03-10 4:07 ` Bagas Sanjaya
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=87mthy7lif.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bagasdotme@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjpark@amazon.de \
/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.