From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:55603 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932118AbeFGK0R (ORCPT ); Thu, 7 Jun 2018 06:26:17 -0400 Date: Thu, 7 Jun 2018 12:26:13 +0200 From: Pavel Machek To: Gao Xiang Cc: Richard Weinberger , LKML , linux-fsdevel , miaoxie@huawei.com, yuchao0@huawei.com, sunqiuyang@huawei.com, fangwei1@huawei.com, liguifu2@huawei.com, weidu.du@huawei.com, chen.chun.yen@huawei.com, brooke.wangzhigang@hisilicon.com, dongjinguang@huawei.com Subject: Re: [NOMERGE] [RFC PATCH 00/12] erofs: introduce erofs file system Message-ID: <20180607102613.GB4372@localhost> References: <1527764767-22190-1-git-send-email-gaoxiang25@huawei.com> <1670077.cnVahIradn@blindfold> <863d726d-e919-9ee1-56e4-994c8ab09f4b@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <863d726d-e919-9ee1-56e4-994c8ab09f4b@huawei.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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