Nested class devices and the future of the device model
Posted Oct 20, 2005 18:57 UTC (Thu) by iabervon
In reply to: Nested class devices and the future of the device model
Parent article: Nested class devices and the future of the device model
If there were an unstable branch, it would presumably break compatibility with 2.6, and it would be intended to become the future arrangement. And you would therefore definitely be wasting effort moving to 2.6, because the stuff you'd use wouldn't even be intended to work long-term. Having stable and unstable branches doesn't in any way resolve compatibility issues; it's just an excuse for breaking things.
I'd even venture to say that the fact that you're still using 2.4 and not 2.6 is that there's a lot of incompatibility due to the 2.5 series in between. Going from 2.6.0 to 2.6.13 breaks compatibility less than 2.4.27 to 2.6.0, even though there is more total change, because there isn't the expectation that there will be a major transition that changes everything.
to post comments)