On Wed, 26 Jul 2006, Pavel Machek wrote:
Hi!
of the story for me. There's nothing wrong about focusing on newer code,
but the old code needs to be cared for, too, to fix remaining issues
such as the "can only have N files with the same hash value".
Requires a disk format change, in a filesystem without plugins, to fix it.
Well, too bad, if reiser3 is so broken it needs on-disk-format-change,
then I guess doing that change is the right thing to do...
Sorry for my stupid question, but could you tell me why starting to make
incompatible changes to reiserfs3 now (when reiserfs3 "technology" is
rather old) and making reiserfs3 unstable (again), possibly for several
months or even years is better than fixing big issues with reiser4 (if
there are any really big left) merging it and trying to stabilize it?
For end user both ways will result in mkfs so...
Thanks,
Grzegorz Kulewski
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
