On Mon, Apr 08, 2013 at 06:51:10PM -0700, Adrian Chadd wrote: > > But then you end up with people making filesystems which aren't > necessarily backwards compatible (and aren't aware of this), then try > to share with other extX implementations; or boot an older Linux > kernel (eg plugging an ext3 device on a newer box to an older box.) > Now, ext3 is a bit more mature nowdays so people aren't _always_ > hitting this corner case. You have a long memory --- going back to about seven years ago, to 2006.... > I'm not knocking extX here; I'm just pointing out that exposing things > as a set of capability flags doesn't magically fix interoperability. > It just stops you from scribbling crap where it shouldn't be. Sure, the only question is how long do you support ancient file systems out there. I consider that primarily a distribution question, not an upstream development question. People who pay $$$ for ancient crud, expect that the people to whom they have paid $$$ will take care of that problem for them. From an upstream development perspective, some people might argue that two years is plenty of time to wait for the vast majority of the people running community distributions to have upgraded (and if they want more than that, they can pay $$$ to the aforementioned enterprise distro's, or take care of that situation on their own). - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
