[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1a3dcbe4-76dd-40c4-bafd-16be33607e77@leemhuis.info>
Date: Wed, 6 Nov 2024 06:26:49 +0100
From: Thorsten Leemhuis <linux@...mhuis.info>
To: Bagas Sanjaya <bagasdotme@...il.com>, Jonathan Corbet <corbet@....net>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-next@...r.kernel.org, Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH v3] docs: bug-bisect: add a note about bisecting -next
On 06.11.24 02:04, Bagas Sanjaya wrote:
> On Tue, Nov 05, 2024 at 01:11:08PM +0100, Thorsten Leemhuis wrote:
>> +Bisecting linux-next
>> +--------------------
>> +
>> +If you face a problem only happening in linux-next, bisect between the
>> +linux-next branches 'stable' and 'master'. The following commands will start
>> +the process for a linux-next tree you added as a remote called 'next'::
>> +
>
> Has linux-next tree remote addition be covered before?
No. That document where this is added does not explain at all how to
clone a git repo or add remotes, it just focuses on the bisection. So I
don't think we need to explain this here.
Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst handles
such things, as it has a different target audience. Should it cover
-next as well? Not sure. I for now decided to focus on this addition.
Ciao, Thorsten
Powered by blists - more mailing lists