git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-bisect(1) next after finding the commit

From
Jeff King <peff@peff.net>
Date
Oct 5, 2026, 03:23 UTC
Message-ID
<20261005032348.GA10163@coredump.intra.peff.net>
In-Reply-To
<asCY8kLEV4OAG1BG@debian>
On Sat, Oct 03, 2026 at 07:59:43AM +0200, Alejandro Colomar wrote:
Show 7 quoted lines
> > 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
Previous: Alejandro ColomarNext: Alejandro Colomar
Message 6 of 7 in “git-bisect(1) next after finding the commit”
  1. Alejandro ColomarOct 2, 2026
  2. Jeff KingOct 2, 2026
  3. Junio C HamanoOct 2, 2026
  4. Alejandro ColomarOct 3, 2026
  5. Alejandro ColomarOct 3, 2026
  6. Jeff KingOct 5, 2026
  7. Alejandro ColomarOct 5, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.