From: Chris Mason <chris.mason@fusionio.com>
To: Alexander Block <ablock84@googlemail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC PATCH 0/6] Experimental btrfs send/receive (btrfs-progs)
Date: Wed, 4 Jul 2012 10:53:53 -0400 [thread overview]
Message-ID: <20120704145353.GL14928@shiny> (raw)
In-Reply-To: <1341409174-13619-1-git-send-email-ablock84@googlemail.com>
On Wed, Jul 04, 2012 at 07:39:28AM -0600, Alexander Block wrote:
> Hello all,
>
> This is the user space side of btrfs send/receive.
>
> You can apply them manually or use my git repo:
>
> git://github.com/ablock84/btrfs-progs.git (branch send)
>
> The branch is based on Hugo's integration-20120605 branch. I had to add a temporary
> commit to fix a bug introduced in one of the strncpy/overflow patches that got into
> btrfs-progs. This fix is not part of the btrfs send/receive patchset, but you'll
> probably need it if you want to base on the integration branch. I hope this is not
> required in the future when a new integration branch comes out.
Just awesome. I'm playing with this now.
Except for the arm patch, I have the integration here in final testing
for 0.20. This stuff will make 0.21 when it is all done.
-chris
next prev parent reply other threads:[~2012-07-04 14:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 13:39 [RFC PATCH 0/6] Experimental btrfs send/receive (btrfs-progs) Alexander Block
2012-07-04 13:39 ` [RFC PATCH 1/6] Btrfs-progs: add BTRFS_IOC_SUBVOL_GET/SETFLAGS to ioctl.h Alexander Block
2012-07-04 13:39 ` [RFC PATCH 2/6] Btrfs-progs: update ioctl.h to support clone range ioctl Alexander Block
2012-07-04 13:39 ` [RFC PATCH 3/6] Btrfs-progs: print inode transid and dir item data field in debug-tree Alexander Block
2012-07-04 13:39 ` [RFC PATCH 4/6] Btrfs-progs: update btrfs-progs for subvol uuid+times support Alexander Block
2012-07-04 13:39 ` [RFC PATCH 5/6] Btrfs-progs: update ioctl.h to support btrfs send ioctl Alexander Block
2012-07-04 13:39 ` [RFC PATCH 6/6] Btrfs-progs: add btrfs send/receive commands Alexander Block
2012-07-09 18:59 ` Alex Lyakas
2012-07-19 13:25 ` Alex Lyakas
2012-07-24 20:27 ` Alexander Block
2012-07-25 9:15 ` Alex Lyakas
2012-07-27 14:06 ` Arne Jansen
2012-07-04 14:53 ` Chris Mason [this message]
2012-07-23 12:29 ` [RFC PATCH 0/6] Experimental btrfs send/receive (btrfs-progs) Arne Jansen
2012-07-25 10:41 ` Alexander Block
2012-07-25 14:00 ` Hugo Mills
2012-07-25 15:17 ` Chris Mason
2012-07-25 16:56 ` Alexander Block
2012-07-25 17:10 ` Alex Lyakas
2012-07-25 17:14 ` Alexander Block
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=20120704145353.GL14928@shiny \
--to=chris.mason@fusionio.com \
--cc=ablock84@googlemail.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 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).