From: "Theodore Ts'o" <tytso@mit.edu>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: nick <xerofoify@gmail.com>,
akpm@linux-foundation.org, fabf@skynet.be,
sasha.levin@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: Remove cramfs source code from mainline kernel?
Date: Wed, 17 Dec 2014 00:07:46 -0500 [thread overview]
Message-ID: <20141217050746.GY17575@thunk.org> (raw)
In-Reply-To: <20141217024602.GG22149@ZenIV.linux.org.uk>
On Wed, Dec 17, 2014 at 02:46:02AM +0000, Al Viro wrote:
>
> 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...
Al, in case you didn't know, Nick Krause has been banned from LKML for
being a troll[1][2][3]. A common troll tactic is to cc a few people
plus the mailing list from which he is banned, in the hopes that
people will get tricked into replying and quoting his original
message, thus evading the ban.
- Ted
[1] https://lkml.org/lkml/2014/8/4/206
[2] http://lists.kernelnewbies.org/pipermail/kernelnewbies/2014-December/012934.html
[3] http://lists.kernelnewbies.org/pipermail/kernelnewbies/2014-December/012938.html
- Ted
prev parent reply other threads:[~2014-12-17 5:07 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 ` Remove cramfs source code from mainline kernel? Al Viro
2014-12-17 5:07 ` Theodore Ts'o [this message]
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=20141217050746.GY17575@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=fabf@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=viro@ZenIV.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.