© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
From a developer pov I actually don't like merge commits, the are a pita. Where merges are nice is for the tree maintainers as they don't have to deal with the individual commit series but track/deal with merge entries. The deeper you go into tree maintainer hiearchy the more important it becomes (basically it is what lets linus scale).
As for how much longer considering bisect keeps lying and saying there is about 12 steps left but the number of commits is not being halved, I have no idea how many more it will go through. This has been the longest most painful bisect I have ever done, not only from the pov of number of builds we have cycled through, but also the number of build failures. For almost every build there have been multiple commits that fail to build. This just shouldn't be happening with upstream commits.
So I took a guess and moved the head manually for this next one, bisect is reporting 706 commits (~10 steps), and if bisect only steps a little, I'll do it again.
next test kernel
http://
based on 62bdb288bf46486