From: D. Ben Knoble <ben.knoble@gmail.com>
Date: Sat, 03 Oct 2026 17:09:39 GMT
Subject: Re: git-visualize(1) plumbing equivalent
Message-ID: <CALnO6CATXadzAfvwEpG7po5dH+scd6KxGxRqXvw6w+zN5krreQ@mail.gmail.com>
In-Reply-To: <37597cc9-0cfe-4a1b-8c7e-1d229c9f7cf0@app.fastmail.com>

On Sat, Oct 3, 2026 at 11:27 AM Kristoffer Haugsbakk
<kristofferhaugsbakk@fastmail.com> wrote:
>
> On Sat, Oct 3, 2026, at 15:45, D. Ben Knoble wrote:
> >[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.

Thanks, TIL.

-- 
D. Ben Knoble