mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Bagas Sanjaya <bagasdotme@gmail.com>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-next@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v3] docs: bug-bisect: add a note about bisecting -next
Date: Wed, 6 Nov 2024 11:35:10 +0100	[thread overview]
Message-ID: <230b7ea7-af9c-4f46-b331-a2df4ae86933@leemhuis.info> (raw)
In-Reply-To: <ZytBuIRztNwrXoe_@archie.me>

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



  reply	other threads:[~2024-11-06 10:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 12:11 Thorsten Leemhuis
2024-11-06  1:04 ` Bagas Sanjaya
2024-11-06  5:26   ` Thorsten Leemhuis
2024-11-06 10:15     ` Bagas Sanjaya
2024-11-06 10:35       ` Thorsten Leemhuis [this message]
2024-11-06 10:41         ` Bagas Sanjaya
2024-11-06 10:43 ` Bagas Sanjaya
2024-11-12 20:07 ` Jonathan Corbet

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=230b7ea7-af9c-4f46-b331-a2df4ae86933@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=bagasdotme@gmail.com \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®