From: Chris Mason <chris.mason@fusionio.com>
To: Alexander Block <ablock84@googlemail.com>
Cc: "hch@infradead.org" <hch@infradead.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: Asking for ACK/NAK on new new Btrfs cross subvolume reflink patch
Date: Tue, 3 Jul 2012 08:13:04 -0400 [thread overview]
Message-ID: <20120703121304.GB14928@shiny> (raw)
In-Reply-To: <CAB9VWqAen0qmwNg1F9mTB2Ft9jbMjGoRWd2-=JXkY1VKyV6V3A@mail.gmail.com>
On Tue, Jul 03, 2012 at 04:39:22AM -0600, Alexander Block wrote:
> Hello Christoph,
>
> I'm writing directly to you (CC only to fsdevel to avoid discussions)
> as we are waiting for a NAK/ACK from you on the
> new cross subvolume reflink patch found in this mail:
> http://www.spinics.net/lists/linux-fsdevel/msg56262.html
> I have the feeling that the new patch is what you asked for in the
> first discussion, but I (and others from Btrfs)
> don't want to add it without you approving it.
I do plan on tacking this one, sharing extents across subvols is really
just an internal part of btrfs. They are separate files, and so there's
no higher level impact.
-chris
next prev parent reply other threads:[~2012-07-03 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 10:39 Asking for ACK/NAK on new new Btrfs cross subvolume reflink patch Alexander Block
2012-07-03 12:13 ` Chris Mason [this message]
2012-07-03 16:13 ` Christoph Hellwig
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=20120703121304.GB14928@shiny \
--to=chris.mason@fusionio.com \
--cc=ablock84@googlemail.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@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).