Re: [Ext2-devel] [RFC 0/13] extents and 48bit ext3
Bodo Eggert <[email protected]>
| Newsgroups | gmane.linux.file-systems,gmane.comp.file-systems.ext2.devel,gmane.linux.kernel |
|---|---|
| Message-ID | <[email protected]> |
grundig <[email protected]> wrote: > Alex Tomas <[email protected]> escribió: >> that's your point of view. mine is that this option (and code) >> to be used only when needed. > > Distros may ignore your opinion and may enable it, and users won't know > that it's enabled or even if such feature exist - until they try to run > an older kernel. If almost nobody needs this feature, why not avoid > problems by not merging it and maintaining it separated from the > main tree? Distros might patch their kernel to support this feature and enable it, therefore you MUST NOT release new features AT ALL!!!1 - NOT If a distro decides to enable a non-backward-compatible feature without warning, it's their fault. BTW: Upgrading a filesystem by using mount options _and_ forcing that option to be supplied on subsequent mounts is a BUG. If should be what current code demands, it should be fixed ASAP. I hope that's not what the current code does. -- Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF verbreiteten Lügen zu sabotieren. http://david.woodhou.se/why-not-spf.html - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html