From: Andreas Schwab <schwab@linux-m68k.org>
To: "Theodore Tso" <tytso@mit.edu>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
git@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"Jonas Rebmann" <kernel@schlaraffenlan.de>,
"Ricardo B. Marlière (SUSE)" <ricardo@marliere.net>
Subject: Re: FYI, git output messages are being used by other tooling
Date: Wed, 21 Oct 2026 20:26:53 +0200 [thread overview]
Message-ID: <87a4o6yknm.fsf@igel.home> (raw)
In-Reply-To: <ate61iEAj4HDIvzY@mit.edu>
On Okt 20 2026, Theodore Tso wrote:
> A structured output that contained the result of the "git bisect
> good|bad", and the first bad commit if it has been found, would be
> certainly be a more reliable way for automated git bisection harneses
> to rely upon. It'd be great if that was something that was in git
> 3.0.
gut rev-parse --bisect shows the bad and the good revisions.
git rev-list $(git rev-parse --bisect) | wc -l gives the number of revs
left to bisect.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2026-10-21 18:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 18:10 FYI, git output messages are being used by other tooling 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-21 17:19 ` Junio C Hamano
2026-10-21 18:26 ` Andreas Schwab [this message]
2026-10-20 19:23 ` Steven Rostedt
2026-10-20 19:28 ` Kristoffer Haugsbakk
2026-10-20 19:33 ` Steven Rostedt
2026-10-20 22:48 ` Theodore Tso
2026-10-21 17:53 ` Kristoffer Haugsbakk
2026-10-20 18:44 ` Kristoffer Haugsbakk
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=87a4o6yknm.fsf@igel.home \
--to=schwab@linux-m68k.org \
--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 \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.