From: Chris Mason <chris.mason@oracle.com>
To: David Morgado <dcrmorgado@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Read Only snapshots
Date: Mon, 25 Apr 2011 08:16:05 -0400 [thread overview]
Message-ID: <1303733730-sup-9388@think> (raw)
In-Reply-To: <BANLkTinngHB+7LMmEGNfAggD0TAy49Fa-Q@mail.gmail.com>
Excerpts from David Morgado's message of 2011-04-24 21:24:16 -0400:
> Hi, btrfs-progs patches for read only snapshots aren't in Chris
> repository yet but btrfs already has support for that in place so,
> someone forgot about this?
>
> It appears that some new patches are coming to Chris btrfs-progs (new
> tmp branch) so this was a nice opportunity to get those patches in.
Right, the tmp branch is the one I'm pushing around and testing for
release. I'll make sure the readonly snapshots code gets in there too.
-chris
next prev parent reply other threads:[~2011-04-25 12:16 UTC|newest]
Thread overview: 14+ 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 [this message]
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 ` [PATCH 0/5] Add user-space support for read-only snapshot creation Li Zefan
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=1303733730-sup-9388@think \
--to=chris.mason@oracle.com \
--cc=dcrmorgado@gmail.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).