On Tuesday 18 September 2007 11:47, Henrique de Moraes Holschuh wrote: > 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.
yes, that can be a problem when you get pulled down into a topic branch with an old root. However, as the topic branches are all pulled into they tree one after another, it should be very quick to determine which one of them is the cause. Topic branches with old roots are also more work for me b/c upstream diverges and I have to repeat merges. for this reason I re-based the cpuidle branch a while back -- as that is by far the oldest one. -Len - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
