On Tue, 18 Sep 2007, Len Brown wrote: > bisecting the acpi git three should work well, because it uses topic branches. > This includes cpuidle. ie. unless the breakage is within the cpuidle branch itself, > the whole cpuidle topic can be removed by skipping the single merge commit that > pulls it in. The issue I had sometimes while bissecting ACPI commits was that the topic branches are often rooted on much earlier versions of the kernel tree. So you are near rcY, and suddenly you are way back to rc(Y-2) while inside one of the ACPI merges... depending on what happened in the large number of non-acpi commits this reverts, that can lead to some annoyance with the resulting kernel. I don't recall if those were bissects of acpi-test, or of mainline though. Maybe my git-fu is simply not up to it, and the above is not a problem for those with better git skills. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
