Re: git-bisect(1) next after finding the commit
- From
- Alejandro Colomar <alx@kernel.org>
- Date
- Oct 5, 2026, 12:37 UTC
- Message-ID
- <asOaBQ_vrF6NC0dW@debian>
- In-Reply-To
- <20261005032348.GA10163@coredump.intra.peff.net>
Hi Jeff,
Show 15 quoted lines
> Date: 2026-10-04 23:23:48-0400 > From: Jeff King <peff@peff.net> > > On Sat, Oct 03, 2026 at 07:59:43AM +0200, Alejandro Colomar wrote: > > > > I'm not 100% sure, but I think "git show bisect/bad" should work. > > > > Thanks! It works. > > > > I guess the plumbing version of it would be > > git rev-list -1 bisect/bad > > right? > > Yeah. Or even just "git rev-parse bisect/bad" (maybe with --verify if > appropriate).
Oh, thanks! I've changed the rev-list -1 calls to do rev-parse.
Have a lovely day! Alex
> -Peff
-- <https://www.alejandro-colomar.es>