[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180607102613.GB4372@localhost>
Date: Thu, 7 Jun 2018 12:26:13 +0200
From: Pavel Machek <pavel@....cz>
To: Gao Xiang <gaoxiang25@...wei.com>
Cc: Richard Weinberger <richard@...ma-star.at>,
LKML <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
miaoxie@...wei.com, yuchao0@...wei.com, sunqiuyang@...wei.com,
fangwei1@...wei.com, liguifu2@...wei.com, weidu.du@...wei.com,
chen.chun.yen@...wei.com, brooke.wangzhigang@...ilicon.com,
dongjinguang@...wei.com
Subject: Re: [NOMERGE] [RFC PATCH 00/12] erofs: introduce erofs file system
Hi!
> >> We also think of other candidate full names, such as
> >> Enhanced / Extented Read-only File System, all the names short for "erofs" are okay.
> >
> > TBH, I read "erofs" as "error fs". ;-)
> eh..."erofs" indeed comes from the EROFS error code, that is a playful behaviour...
> I think the error code of EROFS is not so bad... :'(
For the record, I understood the wordplay before I seen the
explanation, and I like it :-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Powered by blists - more mailing lists