| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 17 Dec 2014 02:46:02 +0000 From: Al Viro <viro@...IV.linux.org.uk> To: nick <xerofoify@...il.com> Cc: akpm@...ux-foundation.org, fabf@...net.be, tytso@....edu, sasha.levin@...cle.com, linux-kernel@...r.kernel.org Subject: Re: Remove cramfs source code from mainline kernel? On Tue, Dec 16, 2014 at 09:14:16PM -0500, nick wrote: > Greetings Andrew and others, > I am wondering as cramfs as been marked obsolete for a while why haven't it been removed? If one of the maintainers can explain why that would be greatly be appreciated. Otherwise I am recommending if there are no good reasons we should remove cramfs from main line as it seems to be only used on systems before squashfs was made main line and well supported from my knowledge. > Cheers, > Nick :) a) learn to use line breaks b) what do we win from removing it? If it starts becoming inconvenient to maintain, it might make sense to consider removal, but as it is... What, somebody has slapped a couple of F-words in there? "FIXME", that is... Al, seriously tempted to add /* FIXME. FIXME. FIXME. DO NOT remove that comment - it serves a very important purpose by tormenting a certain fetishist */ on top of a bunch of files in fs/*.c, just to see what effect will it have... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists