Re: git-visualize(1) plumbing equivalent

From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Oct 3, 2026, 15:26 UTC
Message-ID: <37597cc9-0cfe-4a1b-8c7e-1d229c9f7cf0@app.fastmail.com>
In-Reply-To: <CALnO6CCUY2KF8rEotihdVNy+D10mmzuW0RXbH8nqhSS9jsgQUg@mail.gmail.com>

On Sat, Oct 3, 2026, at 15:45, D. Ben Knoble wrote:

Show 10 quoted lines

>[snip]
> On Sat, Oct 3, 2026 at 6:13 AM Alejandro Colomar <alx@kernel.org> wrote:
>>[snip]
>> The goal is to know whether git-bisect(1) has found a commit yet or not,
>> to stop looping.
>
> I think you are probably looking for the (size of the) set of commits
> between bisect/bad and all the bisect/good-* refs. So you might need
> to "git refs list" the good ones, and feed those as negated refs
> alongside bisect/bad to rev-list?

I think you can do that directly with `git rev-list --bisect` and the other variants that start with `--bisect-`.

I have never used them myself.

>
> In the general case, that wouldn't account for skipped commits as I
> understand it, where multiple commits are left at the end of the
> bisect, but in your script it doesn't look like you skip any.