http://bugzilla.kernel.org/show_bug.cgi?id=8171
------- Additional Comments From [EMAIL PROTECTED] 2007-03-12 12:44 ------- > Follows: v2.6.20-rc7 I'm sorry this line was mis-leading, it also follows 2.6.20. > Precedes: v2.6.21-rc1 Since git keeps track of patch dependencies, and later patches are on top of this one it is simplest to get a git tree, and roll the history back to the exact place that the patch occurred. git bisect start git bisect good v2.6.20 git-bisect bad v2.6.21-rc1 git checkout -b expect-bad 1ba753acb372c2955a4843302e92e49ce82e2fea if good: bit bisect good if bad: git bisect bad git checkout -b expect-good 95befdb398e0112ede80529f6770644ecfa5a82e if good: git bisect good if bad: git bisects bad git visualize The guess here, of course, is that "expect-bad" is bad, and "expect-good" is good. However, if this guess is wrong, you'll be able to continue to use git bisect to look elswhere using bisect's choice of suspects. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
