From: Jeff King <peff@peff.net>
To: Alejandro Colomar <alx@kernel.org>
Cc: git@vger.kernel.org
Subject: Re: git-bisect(1) next after finding the commit
Date: Sun, 4 Oct 2026 23:23:48 -0400 [thread overview]
Message-ID: <20261005032348.GA10163@coredump.intra.peff.net> (raw)
In-Reply-To: <asCY8kLEV4OAG1BG@debian>
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).
-Peff
next prev parent reply other threads:[~2026-10-05 3:23 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 [this message]
2026-10-05 12:37 ` Alejandro Colomar
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=20261005032348.GA10163@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=alx@kernel.org \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox