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

Re: why doesn't "git bisect visualize" show all commit ids from the bisect log

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Sep 20, 2013, 18:22 UTC
Message-ID
<20130920182232.GA30039@google.com>
In-Reply-To
<523C8F0C.6050203@gmx.de>
Hi Toralf,
Toralf Förster wrote:
Show 7 quoted lines
> When run that command immediate after "git bisect start" somebody sees
> the full commit range as defined in "git bisect start".
>
> However running that command later after few git bisect steps" somebody
> is just presented with the remaining commit interval.
>
> Is this intended ?

"git bisect visualize" is meant as a tool to pin down the culprit commit that produced a regression. Sometimes after a few steps the problematic commit is obvious, which can save some test cycles.

If you want to see the list of commits tested so far, "git bisect log" can help. To see the entire bisection state, even outside the regression window, any old "gitk foo..bar" command will do --- the bisection state is kept in bisect/* refs that show up in blue.

Can you say a little more about what you're trying to do? Is the goal to have a nice visualization of what "git bisect log" shows? (I'm not aware of any such tool, and I agree it would be a nice thing.)

Hope that helps, Jonathan

Previous: Toralf FörsterNext: Toralf Förster
Message 2 of 3 in “why doesn't "git bisect visualize" show all commit ids from the bisect log”
  1. Toralf FörsterSep 20, 2013
  2. Jonathan NiederSep 20, 2013
  3. Toralf FörsterSep 20, 2013

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.