On Wednesday 17 October 2007 00:14:26 Bartlomiej Zolnierkiewicz wrote: > Martin, could you run git-bisect (http://kerneltrap.org/node/11753 - sorry > for not explaining the procudure myself but Linus did it really well) > starting with: > > git bisect good 688a87d145e04f6761c63e7f2e19fd9b3e4ca060 > git bisect bad 826a1b6502d0d1d67fc41043fc831e90f2ef5835 > > The "good" one is the last commit before cmd64x changes and the "bad" one > is the first commit after them. Since there is only 5 commits in between > it should be really quick find the bad one (worst-case: 3 > recompiles/reboots). I'll do my best. I appear to have git 1.5.2.2 on my machine, but I've never used it. In the old days we used not to have such luxury! Give me a few days. I shall report back. cu Martin - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
