From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: btrfs-progs: add missing descriptions of '--max-errors' in btrfs-receive documentation
Date: Mon, 11 Aug 2014 11:49:19 +0900 [thread overview]
Message-ID: <53E82F2F.3020800@jp.fujitsu.com> (raw)
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Fix the lack of description of "--max-erros" option in
both man and command usage of btrfs receive.
Signed-off-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
---
Documentation/btrfs-receive.txt | 2 +-
cmds-receive.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/btrfs-receive.txt b/Documentation/btrfs-receive.txt
index 78dc511..beb963c 100644
--- a/Documentation/btrfs-receive.txt
+++ b/Documentation/btrfs-receive.txt
@@ -7,7 +7,7 @@ btrfs-receive - receive subvolumes from stdin/file.
SYNOPSIS
--------
-*btrfs receive* [-ve] [-f <infile>] <mount>
+*btrfs receive* [-ve] [-f <infile>] [--max-errors <N>] <mount>
DESCRIPTION
-----------
diff --git a/cmds-receive.c b/cmds-receive.c
index 9a6d6d9..ed33258 100644
--- a/cmds-receive.c
+++ b/cmds-receive.c
@@ -1120,9 +1120,9 @@ int cmd_receive(int argc, char **argv)
}
const char * const cmd_receive_usage[] = {
- "btrfs receive [-ve] [-f <infile>] <mount>",
+ "btrfs receive [-ve] [-f <infile>] [--max-errors <N>] <mount>",
"Receive subvolumes from stdin.",
- "Receives one or more subvolumes that were previously ",
+ "Receives one or more subvolumes that were previously",
"sent with btrfs send. The received subvolumes are stored",
"into <mount>.",
"btrfs receive will fail in case a receiving subvolume",
--
1.9.3
reply other threads:[~2014-08-11 2:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53E82F2F.3020800@jp.fujitsu.com \
--to=takeuchi_satoru@jp.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.