Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <9c2ea46f-57f9-29e6-7232-c2482acfed15@gmail.com>
Date:   Thu, 10 Mar 2022 11:07:46 +0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.6.2
Subject: Re: [PATCH] Documentation: describe how to apply incremental stable
 patches
Content-Language: en-US
To:     Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc:     SeongJae Park <sjpark@amazon.de>, linux-kernel@vger.kernel.org
References: <20220307063340.256671-1-bagasdotme@gmail.com>
 <87mthy7lif.fsf@meer.lwn.net>
From:   Bagas Sanjaya <bagasdotme@gmail.com>
In-Reply-To: <87mthy7lif.fsf@meer.lwn.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

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