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

Re: git bisect result off by 1 commit

From
TCTim Chen <tim.c.chen@linux.intel.com>
Date
Feb 11, 2013, 17:20 UTC
Message-ID
<1360603230.17632.183.camel@schen9-DESK>
In-Reply-To
<7v1ucqxmyd.fsf@alter.siamese.dyndns.org>
Show 17 quoted lines
> 
> Looks perfectly normal to me.  The message above:
> 
> > HEAD is now at a0d271c... Linux 3.6
> > Bisecting: 0 revisions left to test after this (roughly 0 steps)
> > [d54b1a9e0eaca92cde678d19bd82b9594ed00450] perf script: Remove use of die/exit
> 
> is asking you to test the commit at d54b1a9e and tell it the result
> of the test.  The message says "0 left to test *after* this";
> doesn't it mean you still need to do *this*?
> 
> A bisecct session ends when it tells you
> 
> 	XXXXXX is the first bad commit
> 
> which I do not see in the above.  You seem to have stopped before
> that happens.
Yes, I should do one more step.  Thanks for catching.
Tim
Previous: Junio C Hamano
Message 3 of 3 in “git bisect result off by 1 commit”
  1. Tim ChenFeb 9, 2013
  2. Junio C HamanoFeb 9, 2013
  3. Tim ChenFeb 11, 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.