linux-kernel - Re: [PATCH] Documentation: describe how to apply incremental stable patches

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9c2ea46f-57f9-29e6-7232-c2482acfed15@gmail.com>
Date:   Thu, 10 Mar 2022 11:07:46 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org
Cc:     SeongJae Park <sjpark@...zon.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: describe how to apply incremental stable
 patches

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