From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
linux-doc@vger.kernel.org, SeongJae Park <sjpark@amazon.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: describe how to apply incremental stable patches
Date: Thu, 10 Mar 2022 00:29:52 +0000 [thread overview]
Message-ID: <YilGgO03v+CM0aDq@llamedos.localdomain> (raw)
In-Reply-To: <87mthy7lif.fsf@meer.lwn.net>
On Wed, Mar 09, 2022 at 04:29:28PM -0700, Jonathan Corbet wrote:
> 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
I do. I have several machines with multiple systems (current, old,
older, experimental) and mostly I build current kernels in the
current system, and older LTS in the old systems. Ideally I will
find time to test an rc, but I only use git for kernels when I need
to bisect. I find it much easier to keep the initial relase tarball
and chosen point patches on my local nfs.
My interests are userspace, and some of my machines are
comparatively slow to compile kernels.
ĸen
--
The beauty of reading a page of de Selby is that it leads one
inescapably to the conclusion that one is not, of all nincompoops,
the greatest. -- du Garbandier
next prev parent reply other threads:[~2022-03-10 0:45 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
2022-03-10 0:29 ` Ken Moffat [this message]
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=YilGgO03v+CM0aDq@llamedos.localdomain \
--to=zarniwhoop@ntlworld.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox