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

Is this a git-bisect bug?

From
Wwalt <w41ter@gmail.com>
Date
Feb 21, 2009, 17:07 UTC
Message-ID
<gnpccl$l69$1@ger.gmane.org>
I'm using the current git.git to bisect a bug in Linus.git.

I got this far and then ran into trouble: good 2.6.29-rc5-00094-gc951aa6 bad 2.6.29-rc5-00112-g3501033

A glance at git log will show that those two commits were both from Feb 17 with only one other commit between them.

So, why does this happen?:
$git bisect start 3501033 c951aa6
Bisecting: 8 revisions left to test after this
be716615fe596ee117292dc615e95f707fb67fd1] x86, vm86: fix preemption bug

git log shows that commit is from Jan 13, way back in 2.6.29-rc3. Can anyone reproduce/explain this?

Thanks!
Next: Teemu Likonen
Message 1 of 4 in “Is this a git-bisect bug?”
  1. waltFeb 21, 2009
  2. Teemu LikonenFeb 21, 2009
  3. waltFeb 21, 2009
  4. Christian CouderFeb 22, 2009

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.