{"thread":{"id":"7215","subject":"bisection oddity.","startedAt":"2007-03-12T19:28:21Z","lastAt":"2007-03-12T19:50:56Z","messageCount":2,"participants":["Dave Jones","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"36944","messageId":"20070312192821.GA24992@redhat.com","threadId":"7215","inReplyTo":null,"subject":"bisection oddity.","fromName":"Dave Jones","fromEmail":"davej@redhat.com","sentAt":"2007-03-12T19:28:21Z","receivedAt":"2007-03-12T19:28:21Z","isPatch":false,"sender":{"key":"davej@redhat.com","avatar":null},"body":"I'm chasing a kernel bug that was introduced somewhere between\nv2.6.20 and 2.6.21rc1, and bisect has done this so far..\n\ngit-bisect start\n# bad: [c8f71b01a50597e298dc3214a2f2be7b8d31170c] Linux 2.6.21-rc1\ngit-bisect bad c8f71b01a50597e298dc3214a2f2be7b8d31170c\n# good: [fa285a3d7924a0e3782926e51f16865c5129a2f7] Linux 2.6.20\ngit-bisect good fa285a3d7924a0e3782926e51f16865c5129a2f7\n# bad: [574009c1a895aeeb85eaab29c235d75852b09eb8] Merge branch 'upstream' of git://ftp.linux-mips.org/pub/scm/upstream-linus\ngit-bisect bad 574009c1a895aeeb85eaab29c235d75852b09eb8\n# bad: [43187902cbfafe73ede0144166b741fb0f7d04e1] Merge master.kernel.org:/pub/scm/linux/kernel/git/gregkh/driver-2.6\ngit-bisect bad 43187902cbfafe73ede0144166b741fb0f7d04e1\n# good: [1545085a28f226b59c243f88b82ea25393b0d63f] drm: Allow for 44 bit user-tokens (or drm_file offsets)\ngit-bisect good 1545085a28f226b59c243f88b82ea25393b0d63f\n# good: [c96e2c92072d3e78954c961f53d8c7352f7abbd7] Merge master.kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6\ngit-bisect good c96e2c92072d3e78954c961f53d8c7352f7abbd7\n\nWhat I'm puzzled at is that this lands me at 2.6.20-rc5, which is *before*\nthe range I'm interested in.  What happened here?\n\n\tDave\n\n-- \nhttp://www.codemonkey.org.uk\n"},{"id":"36949","messageId":"Pine.LNX.4.63.0703122047480.22628@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"7215","inReplyTo":"20070312192821.GA24992@redhat.com","subject":"Re: bisection oddity.","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-03-12T19:50:56Z","receivedAt":"2007-03-12T19:50:56Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Mon, 12 Mar 2007, Dave Jones wrote:\n\n> I'm chasing a kernel bug that was introduced somewhere between\n> v2.6.20 and 2.6.21rc1, and bisect has done this so far..\n> \n> git-bisect start\n> # bad: [c8f71b01a50597e298dc3214a2f2be7b8d31170c] Linux 2.6.21-rc1\n> git-bisect bad c8f71b01a50597e298dc3214a2f2be7b8d31170c\n> # good: [fa285a3d7924a0e3782926e51f16865c5129a2f7] Linux 2.6.20\n> git-bisect good fa285a3d7924a0e3782926e51f16865c5129a2f7\n> # bad: [574009c1a895aeeb85eaab29c235d75852b09eb8] Merge branch 'upstream' of git://ftp.linux-mips.org/pub/scm/upstream-linus\n> git-bisect bad 574009c1a895aeeb85eaab29c235d75852b09eb8\n> # bad: [43187902cbfafe73ede0144166b741fb0f7d04e1] Merge master.kernel.org:/pub/scm/linux/kernel/git/gregkh/driver-2.6\n> git-bisect bad 43187902cbfafe73ede0144166b741fb0f7d04e1\n> # good: [1545085a28f226b59c243f88b82ea25393b0d63f] drm: Allow for 44 bit user-tokens (or drm_file offsets)\n> git-bisect good 1545085a28f226b59c243f88b82ea25393b0d63f\n> # good: [c96e2c92072d3e78954c961f53d8c7352f7abbd7] Merge master.kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6\n> git-bisect good c96e2c92072d3e78954c961f53d8c7352f7abbd7\n> \n> What I'm puzzled at is that this lands me at 2.6.20-rc5, which is *before*\n> the range I'm interested in.  What happened here?\n\nThis lands me at\n\nv2.6.20-rc5-301-g31c56d8\n\nwhich is _not_ an ancestor of v2.6.20 (your first good commit), oddly \nenough. Start \"gitk v2.6.20-rc5-301-g31c56d8...v2.6.20\" to see how the \ncommits are related.\n\nSo, it is intended behaviour.\n\nHth,\nDscho\n"}]}