From: Aaron Toponce <aaron.toponce@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: why does btrfs pronounce "butter-eff-ess"?
Date: Mon, 2 Aug 2010 21:38:50 -0600 [thread overview]
Message-ID: <20100803033850.GE28609@achilles.cocyt.us> (raw)
In-Reply-To: <AANLkTimca-wn6wDpENT9t8gTdgFzPXv3uzhtaaHeuySf@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
On Tue, Aug 03, 2010 at 11:27:32AM +0800, Wang Shaoyan wrote:
> As far as I know, btrfs comes from "btree file system", but why does
> btrfs pronounce "butter-eff-ess"?
The same reason we pronounce "ext3" as "eks tee three" rather than "eee
eks tee three"- laziness. "btree file system" is two extra syllables of
inefficiency over "butter fs".
--
. O . O . O . . O O . . . O .
. . O . O O O . O . O O . . O
O O O . O . . O O O O . O O O
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2010-08-03 3:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 3:27 why does btrfs pronounce "butter-eff-ess"? Wang Shaoyan
2010-08-03 3:37 ` Chris Samuel
2010-08-03 3:38 ` Aaron Toponce [this message]
2010-08-03 6:53 ` Tracy Reed
2010-08-07 22:53 ` Gábor Lehel
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=20100803033850.GE28609@achilles.cocyt.us \
--to=aaron.toponce@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).