From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: 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 11:07:46 +0700 [thread overview]
Message-ID: <9c2ea46f-57f9-29e6-7232-c2482acfed15@gmail.com> (raw)
In-Reply-To: <87mthy7lif.fsf@meer.lwn.net>
On 10/03/22 06.29, Jonathan Corbet wrote:
> 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?
>
I think most people don't use Git to track kernel sources, so they just
download full tarball from kernel.org, then applying stable update
patches (normal or incremental). I also used to do the same, but now I use
Git because when there is stable kernel update, I can simply `git fetch`,
then checkout desired stable branch, and `git merge`.
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2022-03-10 4:07 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
2022-03-10 4:07 ` Bagas Sanjaya [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=9c2ea46f-57f9-29e6-7232-c2482acfed15@gmail.com \
--to=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;
as well as URLs for NNTP newsgroup(s).