From: Kristoffer Haugsbakk Date: Tue, 20 Oct 2026 18:44:41 GMT Subject: Re: FYI, git output messages are being used by other tooling Message-ID: <095638e2-3e01-4217-8f08-3f9cb7fe8a07@app.fastmail.com> 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.