From: Li Zefan <lizf@cn.fujitsu.com>
To: Andreas Philipp <philipp.andreas@gmail.com>
Cc: linux-btrfs@vger.kernel.org, chris.mason@oracle.com,
dcrmorgado@gmail.com
Subject: Re: [PATCH 0/5] Add user-space support for read-only snapshot creation.
Date: Tue, 26 Apr 2011 13:42:31 +0800 [thread overview]
Message-ID: <4DB65B47.5060803@cn.fujitsu.com> (raw)
In-Reply-To: <1303739282-1675-1-git-send-email-philipp.andreas@gmail.com>
Andreas Philipp wrote:
> There is kernel side support for the creation of read-only snapshots
> for some time now, but I did not find any patches for the userspace
> btrfs utilites. Thus I created this patchset which is tested and
> working with kernel version 2.6.39-rc2.
>
> Andreas Philipp (5):
> Add support for read-only subvolumes.
> Support the new parameters in do_clone(int argc, char** argv).
> Added support for an additional ioctl.
> Test the additional ioctl.
> Updated documentation for btrfs subvolume snapshot.
>
Thanks for doing this!
next prev parent reply other threads:[~2011-04-26 5:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 1:24 Read Only snapshots David Morgado
2011-04-25 12:16 ` Chris Mason
2011-04-25 13:47 ` [PATCH 0/5] Add user-space support for read-only snapshot creation Andreas Philipp
2011-04-25 13:47 ` [PATCH 1/5] Add support for read-only subvolumes Andreas Philipp
2011-04-25 21:34 ` Goffredo Baroncelli
2011-04-25 23:24 ` Chris Mason
2011-04-26 6:06 ` Li Zefan
2011-04-26 5:48 ` Li Zefan
2011-04-26 5:50 ` Li Zefan
2011-04-25 13:47 ` [PATCH 2/5] Support the new parameters in do_clone(int argc, char** argv) Andreas Philipp
2011-04-25 13:47 ` [PATCH 3/5] Added support for an additional ioctl Andreas Philipp
2011-04-25 13:48 ` [PATCH 4/5] Test the " Andreas Philipp
2011-04-25 13:48 ` [PATCH 5/5] Updated documentation for btrfs subvolume snapshot Andreas Philipp
2011-04-26 5:42 ` Li Zefan [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-13 9:12 [PATCH 0/5] Add user-space support for read-only snapshot creation Andreas Philipp
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=4DB65B47.5060803@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=dcrmorgado@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=philipp.andreas@gmail.com \
/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).