From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: send operates on ro snapshots only
Date: Tue, 6 Jun 2017 05:41:33 +0000 (UTC) [thread overview]
Message-ID: <pan$442fa$c52a63d2$b43f5df4$7921ee00@cox.net> (raw)
In-Reply-To: 20170605233218.12421-1-hans.van.kranenburg@mendix.com
Hans van Kranenburg posted on Tue, 06 Jun 2017 01:32:18 +0200 as
excerpted:
> While talking to another btrfs user on IRC today, it became clear that a
> major point of confusion in the btrfs send manual is that it's not
> telling the user soon enough that send/receive solely operates on
> subvolume snapshots instead of the original (read/write) subvolumes.
>
> So, change the first few alineas to explicitely mention snapshots
... lines to explicitly ...
> instead. Technically, snapshots are also just subvolumes, but requiring
> this level of technical detailed knowledge doesn't help the user which
> is just trying out things.
[actual patch omitted]
LGTM (other than the commit description spelling as above, neither my
read-thru nor the spellchecker flagged anything in the actual patch).
The new wording is indeed much clearer. Thanks. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-06-06 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 23:32 [PATCH] btrfs-progs: send operates on ro snapshots only Hans van Kranenburg
2017-06-06 5:41 ` Duncan [this message]
2017-06-06 13:00 ` [PATCH v2] " Hans van Kranenburg
2017-06-12 14:04 ` David Sterba
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='pan$442fa$c52a63d2$b43f5df4$7921ee00@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).