From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: free space inode generation (0) did not match free space cache generation
Date: Tue, 25 Mar 2014 21:28:20 +0000 (UTC) [thread overview]
Message-ID: <pan$3d66d$3387207$cd903ed1$f8b0a27f@cox.net> (raw)
In-Reply-To: 20140325201020.GC7442@carfax.org.uk
Hugo Mills posted on Tue, 25 Mar 2014 20:10:20 +0000 as excerpted:
> Did you mean "fated": intended, destined?
No, I meant "feted", altho I understand in Europe the first "e" would
likely have a carot-hat (fêted), but us US-ASCII folks don't have such a
thing easily available, so unless I copy/paste as I just did or use
charselect, "feted" without the carot it is.
Where I've seen "feted" used it tends to have a slightly future-
predictive hint to it, something that's considered a "shoe-in" to use
another term, but that isn't necessarily certain just yet. Alternatively
or as well, it can mean something that many or the majority considers/
celebrates as true, but that the author isn't necessarily taking a
particular position on at this time, perhaps as part of the traditional
journalist's neutral observer's perspective, saying "other people
celebrate it as", without personally 100% endorsing the same position.
Which fit my usage exactly. I wanted to indicate that btrfs' position as
a successor to the ext3/4 throne is a widely held expectation, but that
while I agree with the general sentiment, it's with a "wait and see if/
when these few details get fixed" attitude, because I don't think that a
btrfs that a knowledgeable admin must babysit in ordered to be sure it
doesn't run out of unallocated chunks, for example, is quite ready for
usage by "the masses", that is, to take the throne as crowned successor
to ext3/4 just yet. And "feted" seemed the perfect word to express and
acknowledge that expectation, while at the same time conveying my slight
personal reservation.
In fact, until I looked up the word I had no idea the word could also be
used as a noun in addition to my usage as a verb, and used as a noun,
that it meant a feast, celebration or carnival. I was familiar only with
the usage I demonstrated here, including the slight hint of third party
neutrality or wait-and-see reservation, which was in fact my reason for
choosing the term in the first place.
(This is of course one reason I so enjoy newsgroups and mailing lists.
One never knows what sort of entirely unpredicted but useful thing one
might learn from them, even in my own replies sometimes! =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-03-25 21:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <532DF38B.40409@friedels.name>
2014-03-22 21:16 ` free space inode generation (0) did not match free space cache generation Hendrik Friedel
2014-03-22 23:32 ` Duncan
2014-03-24 20:52 ` Hendrik Friedel
2014-03-25 13:00 ` Duncan
2014-03-25 20:03 ` Hendrik Friedel
2014-03-25 20:10 ` Hugo Mills
2014-03-25 21:28 ` Duncan [this message]
2014-03-25 21:50 ` Hugo Mills
2014-03-28 7:32 ` Hendrik Friedel
2014-03-22 18:13 Hendrik Friedel
2014-03-22 19:23 ` Duncan
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='pan$3d66d$3387207$cd903ed1$f8b0a27f@cox.net' \
--to=1i5t5.duncan@cox.net \
--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 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.