From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Thorsten Leemhuis <linux@leemhuis.info>,
Linux kernel regressions list <regressions@lists.linux.dev>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: More detailed text about bisecting Linux kernel regression -- request for comments and help
Date: Sun, 28 Jan 2024 09:18:34 +0700 [thread overview]
Message-ID: <ZbW5emVndDNZlPTg@archie.me> (raw)
In-Reply-To: <c763e15e-e82e-49f8-a540-d211d18768a3@leemhuis.info>
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
On Wed, Jan 24, 2024 at 01:19:16PM +0100, Thorsten Leemhuis wrote:
> .. _bisectstart_bissbs:
>
> * Start the bisection and tell Git about the versions earlier
> established as 'good' and 'bad'::
>
> cd ~/linux/
> git bisect start
> git bisect good v6.0
> git bisect bad v6.1.5
If stable release tag is supplied instead as "good" version instead (e.g.
v6.0.1), as in many regression cases, git will ask to test the merge base
instead, which is corresponding mainline release (in this case v6.0).
Thanks.
--
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-01-28 2:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 12:19 More detailed text about bisecting Linux kernel regression -- request for comments and help Thorsten Leemhuis
2024-01-25 9:36 ` Jani Nikula
2024-01-25 10:28 ` Thorsten Leemhuis
2024-01-25 12:54 ` Jani Nikula
2024-01-28 2:18 ` Bagas Sanjaya [this message]
2024-01-28 5:28 ` Thorsten Leemhuis
2024-01-28 12:27 ` Bagas Sanjaya
2024-02-05 8:32 ` Linux regression tracking (Thorsten Leemhuis)
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=ZbW5emVndDNZlPTg@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).