| |||||||||||||
Why some drivers are not merged earlyWhy some drivers are not merged earlyPosted Jun 21, 2008 8:17 UTC (Sat) by mitchskin (subscriber, #32405)Parent article: Why some drivers are not merged early
On the other hand, the idea that in-tree code tends to be less buggy than out-of-tree code is relatively uncontroversial. So, for many drivers at least, a "merge first and fix it up later" policy may well lead to the best results in the shortest period of time.Maybe having high hurdles to inclusion is what makes in-tree code less buggy in the first place? One wonders whether adopting the approach advocated by the second sentence above might make the first sentence less truthful.
(Log in to post comments)
Why some drivers are not merged early Posted Jun 22, 2008 17:54 UTC (Sun) by man_ls (subscriber, #15091) [Link] Sure, but to what degree? That is the interesting question, and it can be formulated as a trade-off. Is the increase in quality worth the initial bugginess?
|
|||||||||||||