From: Alejandro Colomar <alx@kernel.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: git-bisect(1) next after finding the commit
Date: Mon, 5 Oct 2026 14:37:57 +0200 [thread overview]
Message-ID: <asOaBQ_vrF6NC0dW@debian> (raw)
In-Reply-To: <20261005032348.GA10163@coredump.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
Hi Jeff,
> 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>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-10-05 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 21:49 git-bisect(1) next after finding the commit Alejandro Colomar
2026-10-02 22:11 ` Jeff King
2026-10-02 22:32 ` Junio C Hamano
2026-10-03 6:03 ` Alejandro Colomar
2026-10-03 5:59 ` Alejandro Colomar
2026-10-05 3:23 ` Jeff King
2026-10-05 12:37 ` Alejandro Colomar [this message]
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=asOaBQ_vrF6NC0dW@debian \
--to=alx@kernel.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.