From: Chris Mason <chris.mason@fusionio.com>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: Chris Mason <clmason@fusionio.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"mfasheh@suse.de" <mfasheh@suse.de>,
"alex.btrfs@zadarastorage.com" <alex.btrfs@zadarastorage.com>
Subject: Re: [PATCH v2] Btrfs: extended inode refs support for send mechanism
Date: Tue, 16 Oct 2012 16:58:36 -0400 [thread overview]
Message-ID: <20121016205836.GC7339@shiny> (raw)
In-Reply-To: <1350289845-18604-1-git-send-email-list.btrfs@jan-o-sch.net>
On Mon, Oct 15, 2012 at 02:30:45AM -0600, Jan Schmidt wrote:
> This adds support for the new extended inode refs to btrfs send.
Thanks, pulling this in.
-chris
prev parent reply other threads:[~2012-10-16 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 8:30 [PATCH v2] Btrfs: extended inode refs support for send mechanism Jan Schmidt
2012-10-16 20:11 ` Mark Fasheh
2012-10-16 20:58 ` Chris Mason [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=20121016205836.GC7339@shiny \
--to=chris.mason@fusionio.com \
--cc=alex.btrfs@zadarastorage.com \
--cc=clmason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
--cc=mfasheh@suse.de \
/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).