From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Feature Req: "mkfs.btrfs -d dup" option on single device
Date: Wed, 11 Dec 2013 07:39:48 +0000 (UTC) [thread overview]
Message-ID: <pan$ad9b0$fed0d7f$4713fad4$6845a26d@cox.net> (raw)
In-Reply-To: B4C47427-3A7F-4ED8-85AA-FA8E17C39EF9@colorremedies.com
Chris Murphy posted on Tue, 10 Dec 2013 17:33:59 -0700 as excerpted:
> On Dec 10, 2013, at 5:14 PM, Imran Geriskovan
> <imran.geriskovan@gmail.com> wrote:
>
>> As being the lead developer, is it possible for you to
>> provide some insights for the reliability of this option?
>
> I'm not a developer, I'm just an ape who wears pants. Chris Mason is the
> lead developer.
Lest anyone stumbling across this in a google or the like think
otherwise, it's probably worthwhile to pull this bit out in its own post.
Chris Mason: btrfs lead dev.
Chris Murphy: not a dev, just a btrfs tester/user and btrfs list regular.
It's worth noting that this isn't a problem unique to this list or the
Chris name. There are I think three "Linus" on LKML now, with at least
Linus W noting in good humor at one point that his posts do tend to get
noticed a bit more due to his first name, even if he's not /the/ Linus,
Torvalds, that is.
I've name-collided with other "John Duncan"s too. Which is one reason
I've been a mononym "Duncan" for over a decade now. Strangely enough,
I've had far fewer issues with Duncan as a mononym, than I did with "John
Duncan". I guess at least the "Duncan" mononym is rarer than the "John
Duncan" name.
@ C. Murphy: Given the situation, you might consider a "not a dev, just
a user" disclaimer in your sig... Or perhaps you'll find a Murphy mononym
as useful as I have the Duncan mononym, altho I guess that has the
Murphy's Law connotation, but that might have the effect of keeping the
namespace even clearer (or not, I don't know), as well as making the
mononym rather more memorable!
--
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:[~2013-12-11 7:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 20:31 Feature Req: "mkfs.btrfs -d dup" option on single device Imran Geriskovan
2013-12-10 22:41 ` Chris Murphy
2013-12-10 23:33 ` Imran Geriskovan
2013-12-10 23:40 ` Chris Murphy
[not found] ` <CAK5rZE6DVC5kYAU68oCjjzGPS4B=nRhOzATGM-5=m1_bW4GG6g@mail.gmail.com>
2013-12-11 0:17 ` Fwd: " Imran Geriskovan
2013-12-11 0:33 ` Chris Murphy
2013-12-11 3:19 ` Imran Geriskovan
2013-12-11 4:07 ` Chris Murphy
2013-12-11 8:09 ` Hugo Mills
2013-12-11 16:15 ` Chris Murphy
2013-12-11 17:46 ` Duncan
2013-12-11 14:07 ` Martin
2013-12-11 15:31 ` Imran Geriskovan
2013-12-11 23:32 ` SSD data retention, was: " Chris Murphy
2013-12-11 7:39 ` Duncan [this message]
2013-12-11 10:56 ` Feature Req: " Duncan
2013-12-11 13:19 ` Imran Geriskovan
2013-12-11 18:27 ` Duncan
2013-12-12 15:57 ` Chris Mason
2013-12-12 17:58 ` David Sterba
2013-12-13 9:33 ` Duncan
2013-12-17 18:37 ` Imran Geriskovan
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$ad9b0$fed0d7f$4713fad4$6845a26d@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.