[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <230b7ea7-af9c-4f46-b331-a2df4ae86933@leemhuis.info>
Date: Wed, 6 Nov 2024 11:35:10 +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 11:15, Bagas Sanjaya wrote:
> On Wed, Nov 06, 2024 at 06:26:49AM +0100, Thorsten Leemhuis wrote:
>> On 06.11.24 02:04, Bagas Sanjaya wrote:
>>> On Tue, Nov 05, 2024 at 01:11:08PM +0100, Thorsten Leemhuis wrote:
>
>> 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.
>
> I think for those who want to test linux-next, they can simply follow [1].
> Maybe we can add a pointer to it.
> [1]: https://www.kernel.org/doc/man-pages/linux-next.html
Don't think that's worth it either for this document, as those that want
to bisect -next most of the time will already have retrieved next via
git. And again: providing such a pointer for -next, but not explaining
how to retrieve mainline (which is left to the other document linked
prominently at the top) IMHO makes no sense either.
Ciao, Thorsten
Powered by blists - more mailing lists