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

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

From
TFToralf Förster <toralf.foerster@gmx.de>
Date
Sep 20, 2013, 18:08 UTC
Message-ID
<523C8F0C.6050203@gmx.de>

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 ?
-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
Next: Jonathan Nieder
Message 1 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.