From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Thorsten Leemhuis <linux@leemhuis.info>,
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 17:15:20 +0700 [thread overview]
Message-ID: <ZytBuIRztNwrXoe_@archie.me> (raw)
In-Reply-To: <1a3dcbe4-76dd-40c4-bafd-16be33607e77@leemhuis.info>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
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:
> >> +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.
OK.
>
> 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.
Thanks.
[1]: https://www.kernel.org/doc/man-pages/linux-next.html
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-11-06 10:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 12:11 [PATCH v3] docs: bug-bisect: add a note about bisecting -next Thorsten Leemhuis
2024-11-06 1:04 ` Bagas Sanjaya
2024-11-06 5:26 ` Thorsten Leemhuis
2024-11-06 10:15 ` Bagas Sanjaya [this message]
2024-11-06 10:35 ` Thorsten Leemhuis
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=ZytBuIRztNwrXoe_@archie.me \
--to=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 \
--cc=linux@leemhuis.info \
/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