Using git-core-0.99.6 I tried to locate a bug using git's bisection
searching.
It gave the wrong answer. It ended up claiming the bug was in
tree ea7b1763aa0e0d36b52fa245449c79338fe735b3
parent e9f86e351fda5b3c40192fc3990453613f160779
author Zachary Amsden <[EMAIL PROTECTED]> Sun, 04 Sep 2005 05:56:47 -0700
committer Linus Torvalds <[EMAIL PROTECTED]> Mon, 05 Sep 2005 14:06:13 -0700
[PATCH] x86: introduce a write acessor for updating the current LDT
Whereas the bug was really in
tree 090c471fdb44d8fe88c52e95be0e8e43e31fcd5a
parent d7271b14b2e9e5905aba0fbf5c4dc4f8980c0cb2
author Zwane Mwaikambo <[EMAIL PROTECTED]> Sun, 04 Sep 2005 05:56:51 -0700
committer Linus Torvalds <[EMAIL PROTECTED]> Mon, 05 Sep 2005 14:06:13 -0700
[PATCH] i386 boottime for_each_cpu broken
Which is off-by-two, iirc.
Exact sequence:
bix:/usr/src/git26> git bisect start
bix:/usr/src/git26> git bisect good 02b3e4e2d71b6058ec11cc01c72ac651eb3ded2b
bix:/usr/src/git26> git bisect bad 4e1491847ef5ca1c5a661601d5f96dcb7d90d2f0
Bisecting: 901 revisions left to test after this
bix:/usr/src/git26> git bisect good
Bisecting: 451 revisions left to test after this
bix:/usr/src/git26> git bisect bad
Bisecting: 219 revisions left to test after this
bix:/usr/src/git26> git bisect bad
Bisecting: 110 revisions left to test after this
bix:/usr/src/git26> git bisect bad
Bisecting: 55 revisions left to test after this
bix:/usr/src/git26> git bisect bad
Bisecting: 28 revisions left to test after this
bix:/usr/src/git26> git bisect good
Bisecting: 14 revisions left to test after this
bix:/usr/src/git26> git bisect good
Bisecting: 7 revisions left to test after this
bix:/usr/src/git26> git bisect good
Bisecting: 3 revisions left to test after this
bix:/usr/src/git26> git bisect bad
Bisecting: 2 revisions left to test after this
bix:/usr/src/git26> git bisect good
f2f30ebca6c0c95e987cb9a1fd1495770a75432e is first bad commit
diff-tree f2f30ebca6c0c95e987cb9a1fd1495770a75432e (from
e9f86e351fda5b3c40192fc3990453613f160779)
Author: Zachary Amsden <[EMAIL PROTECTED]>
Date: Sat Sep 3 15:56:47 2005 -0700
[PATCH] x86: introduce a write acessor for updating the current LDT
I don't think I screwed anything up.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html