[PATCH] btrfs-progs: describe btrfs-send requires read-only subvolume

[PATCH] btrfs-progs: describe btrfs-send requires read-only subvolume

[Satoru Takeuchi]

Both man btrfs-send(8) and usage message don't describe
btrfs-send needs read-only snapshot as its argument.

Signed-off-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
---
 Documentation/btrfs-send.asciidoc | 1 +
 cmds-send.c                       | 1 +
 2 files changed, 2 insertions(+)

diff --git a/Documentation/btrfs-send.asciidoc b/Documentation/btrfs-send.asciidoc
index 1dba8a3..e05342f 100644
--- a/Documentation/btrfs-send.asciidoc
+++ b/Documentation/btrfs-send.asciidoc
@@ -12,6 +12,7 @@ SYNOPSIS
 DESCRIPTION
 -----------
 Sends the subvolume(s) specified by <subvol> to stdout.
+<subvol> should be read-only here.
 
 By default, this will send the whole subvolume. To do an incremental
 send, use '-p <parent>'.
diff --git a/cmds-send.c b/cmds-send.c
index 478ace1..3e34d75 100644
--- a/cmds-send.c
+++ b/cmds-send.c
@@ -711,6 +711,7 @@ const char * const cmd_send_usage[] = {
 	"btrfs send [-ve] [-p <parent>] [-c <clone-src>] [-f <outfile>] <subvol> [<subvol>...]",
 	"Send the subvolume(s) to stdout.",
 	"Sends the subvolume(s) specified by <subvol> to stdout.",
+	"<subvol> should be read-only here.",
 	"By default, this will send the whole subvolume. To do an incremental",
 	"send, use '-p <parent>'. If you want to allow btrfs to clone from",
 	"any additional local snapshots, use '-c <clone-src>' (multiple times",
-- 
2.5.0

Re: [PATCH] btrfs-progs: describe btrfs-send requires read-only subvolume

[David Sterba]

On Thu, Feb 04, 2016 at 02:02:14PM +0900, Satoru Takeuchi wrote:
> Both man btrfs-send(8) and usage message don't describe
> btrfs-send needs read-only snapshot as its argument.
> 
> Signed-off-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>

Applied, thanks.