From: Hugo Mills <hugo@carfax.org.uk>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: mkfs: allow DUP on multidev fs, only warn
Date: Fri, 25 Mar 2016 03:58:58 +0000 [thread overview]
Message-ID: <20160325035858.GD29474@carfax.org.uk> (raw)
In-Reply-To: <pan$83413$34f18f9e$a1606444$9239e69f@cox.net>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
On Fri, Mar 25, 2016 at 01:59:20AM +0000, Duncan wrote:
> David Sterba posted on Thu, 24 Mar 2016 16:56:13 +0100 as excerpted:
>
> > The DUP profile can work on multiple filesystems, the limitation is
> > rather artificial. Let the user make the decision and print a warning.
> >
> > Signed-off-by: David Sterba <dsterba@suse.com>
> > ---
>
> I like the change, but typo in the commit comment... What filesystems
> other than btrfs allow DUP? =:^) It's correct in the posting subject.
Class/instance problem. :)
Is that class of filesystems, btrfs, or instance of a btrfs
filesystem? "Filesystem" covers both cases.
Hugo, Ontologist(*).
(*) Yes, that's actually my job title these days.
--
Hugo Mills | Be pure.
hugo@... carfax.org.uk | Be vigilant.
http://carfax.org.uk/ | Behave.
PGP: E2AB1DE4 | Torquemada, Nemesis
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2016-03-25 3:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 15:56 [PATCH] btrfs-progs: mkfs: allow DUP on multidev fs, only warn David Sterba
2016-03-25 1:55 ` [PATCH] btrfs-progs: mkfs: fix an error when using DUP on multidev fs Satoru Takeuchi
2016-03-30 14:20 ` David Sterba
2016-03-25 1:59 ` [PATCH] btrfs-progs: mkfs: allow DUP on multidev fs, only warn Duncan
2016-03-25 3:58 ` Hugo Mills [this message]
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=20160325035858.GD29474@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=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.