I have only more frustration for you: kernel #36 is untestable (same as #6, #11, #16, #21). Back when I was trying this myself, I recall reading "but git may eventually be unable to tell the first bad commit among a bad commit and one or more skipped commits" in the documentation. Perhaps that is why it seems to be making very poor choices of what commit to test next.
When I asked, long ago, about consequences for breaking the build, I meant that in any project I've worked on (all much smaller than this), if someone committed non-building code, that was the end of their privileges to do so without supervision. As many bad commits as there are in this project, I don't know what to think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/793437 Title: Unusable Slowness In 2.6.38-8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/793437/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
