From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Steven Rostedt" <rostedt@goodmis.org>, git@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
"Jonas Rebmann" <kernel@schlaraffenlan.de>,
"Junio C Hamano" <gitster@pobox.com>,
"Ricardo B. Marlière (SUSE)" <ricardo@marliere.net>
Subject: Re: FYI, git output messages are being used by other tooling
Date: Tue, 20 Oct 2026 20:44:41 +0200 [thread overview]
Message-ID: <095638e2-3e01-4217-8f08-3f9cb7fe8a07@app.fastmail.com> (raw)
In-Reply-To: <20261020141011.0015d172@gandalf.local.home>
On Tue, Oct 20, 2026, at 20:10, Steven Rostedt wrote:
> Hi,
>
> I just want to let you folks know that ktest.pl (tools/testing/ktest/ in
> the Linux kernel repository) parses the output of git to display the first
> bad commit found in an automated git bisect.
>
> The output was recently updated via: 0c0f93e7fa64 ("bisect: print bisect
> terms in single quotes") which made ktest.pl fail to find the bad commit.
>
> The change is being addressed:
>
>
> https://lore.kernel.org/all/20261009-ktest-git-bisect-v1-1-1d1428f6cbf4@marliere.net/
>
> But I figured it would be good for you to know about this dependency.
There were recent threads about how to
query for the first bad commit.
https://lore.kernel.org/git/asAbOSQ4BkuCTPY5@debian/
I had a recent script that I put on hold and didn't
finish. But it involved using exit codes and querying
for things like ref state. And maybe using
git rev-list --bisect.
prev parent reply other threads:[~2026-10-20 18:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 18:10 Steven Rostedt
2026-10-20 18:37 ` Junio C Hamano
2026-10-20 18:52 ` Steven Rostedt
2026-10-20 19:09 ` Theodore Tso
2026-10-20 19:23 ` Steven Rostedt
2026-10-20 19:28 ` Kristoffer Haugsbakk
2026-10-20 19:33 ` Steven Rostedt
2026-10-20 18:44 ` Kristoffer Haugsbakk [this message]
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=095638e2-3e01-4217-8f08-3f9cb7fe8a07@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kernel@schlaraffenlan.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ricardo@marliere.net \
--cc=rostedt@goodmis.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®