From: Al Viro <viro@ZenIV.linux.org.uk>
To: nick <xerofoify@gmail.com>
Cc: akpm@linux-foundation.org, fabf@skynet.be, tytso@mit.edu,
sasha.levin@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: Remove cramfs source code from mainline kernel?
Date: Wed, 17 Dec 2014 02:46:02 +0000 [thread overview]
Message-ID: <20141217024602.GG22149@ZenIV.linux.org.uk> (raw)
In-Reply-To: <5490E6F8.4030207@gmail.com>
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...
next parent reply other threads:[~2014-12-17 2:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5490E6F8.4030207@gmail.com>
2014-12-17 2:46 ` Al Viro [this message]
2014-12-17 5:07 ` Remove cramfs source code from mainline kernel? Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141217024602.GG22149@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=fabf@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=tytso@mit.edu \
--cc=xerofoify@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox