From: David Sterba <dsterba@suse.cz>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] Btrfs-progs: add dedup subcommand
Date: Mon, 2 Sep 2013 18:33:34 +0200 [thread overview]
Message-ID: <20130902163334.GD23113@twin.jikos.cz> (raw)
In-Reply-To: <20130812024554.GA19701@localhost.localdomain>
On Mon, Aug 12, 2013 at 10:45:55AM +0800, Liu Bo wrote:
> On Fri, Aug 09, 2013 at 02:51:35PM +0200, David Sterba wrote:
> > I'm not sure that calling it register/unregister is the right thing, IMO
> > it's more enable/disable as you write in the documentation under each
> > respective command.
> >
>
> Both of them are easy to be understood, but let's keep it consistent
> with the docs as you suggest :)
I'm now adding the dedup patch into integration so more people can play
with it (though the kernel part is not in btrfs-next yet). I've
committed a separate patch to do the rename, but feel free to fold it
into further revisions of your progs dedup patch, I'll drop mine then.
david
prev parent reply other threads:[~2013-09-02 16:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 8:35 [RFC PATCH v6 0/5] Online data deduplication Liu Bo
2013-08-08 8:35 ` [RFC PATCH v6 1/5] Btrfs: skip merge part for delayed data refs Liu Bo
2013-08-08 8:35 ` [RFC PATCH v6 2/5] Btrfs: improve the delayed refs process in rm case Liu Bo
2013-08-08 8:35 ` [RFC PATCH v6 3/5] Btrfs: introduce a head ref rbtree Liu Bo
2013-08-08 8:35 ` [RFC PATCH v6 4/5] Btrfs: disable qgroups accounting when quata_enable is 0 Liu Bo
2013-08-08 8:35 ` [RFC PATCH v6 5/5] Btrfs: online data deduplication Liu Bo
2013-09-02 16:19 ` David Sterba
2013-09-09 6:15 ` Liu Bo
2013-08-08 8:35 ` [PATCH v2] Btrfs-progs: add dedup subcommand Liu Bo
2013-08-09 12:51 ` David Sterba
2013-08-12 2:45 ` Liu Bo
2013-09-02 16:33 ` David Sterba [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=20130902163334.GD23113@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=bo.li.liu@oracle.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 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.