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

Re: [BUG] Git bisect not finding the right commit

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Jan 19, 2012, 08:23 UTC
Message-ID
<4F17D2E5.7000400@viscovery.net>
In-Reply-To
<87r4yw8j4i.fsf@franz.ak.mind.de>
Am 1/19/2012 4:29, schrieb Andreas J. Koenig:
Show 10 quoted lines
> 	- A -> B      ->     C - D ->
> 	         \         /
> 	          - E - F -
> 
> A v5.15.5
> B v5.15.5-20-gfd76d40
> C v5.15.5-81-gcfe287a
> D v5.15.5-159-ga71d67b
> E v5.15.4-110-g27b29ec
> F v5.15.4-169-g3582575

I haven't looked at the actual history, but given the names of the commits as produced by git-describe, I doubt that your history graph sketched above is correct. Doesn't it look more like this:

      A -- B -- C -- D --
     /         /
 -- X -- E -- F
where X is v5.15.4?
To find a commit between A and B, you must declare F as "good".
-- Hannes
Previous: Jeff King
Message 6 of 6 in “[BUG] Git bisect not finding the right commit”
  1. Andreas J. KoenigJan 19, 2012
  2. Junio C HamanoJan 19, 2012
  3. Andreas J. KoenigJan 20, 2012
  4. Junio C HamanoJan 20, 2012
  5. Jeff KingJan 24, 2012
  6. Johannes SixtJan 19, 2012

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.