From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs-progs: Documentations: Fix a format error in btrfs-replace.txt
Date: Thu, 7 Aug 2014 19:25:52 +0900 [thread overview]
Message-ID: <53E35430.9070408@jp.fujitsu.com> (raw)
In-Reply-To: <1407137334-6183-1-git-send-email-quwenruo@cn.fujitsu.com>
(2014/08/04 16:28), Qu Wenruo wrote:
> Missing '+'s cause '-B' option not displayed correctly, add it to fix.
>
> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
Reviewed-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Tested-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
> ---
> Documentation/btrfs-replace.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/btrfs-replace.txt b/Documentation/btrfs-replace.txt
> index eecf9b0..067b02d 100644
> --- a/Documentation/btrfs-replace.txt
> +++ b/Documentation/btrfs-replace.txt
> @@ -42,6 +42,7 @@ The <targetdev> needs to be same size or larger than the <srcdev>.
> only read from <srcdev> if no other zero-defect mirror exists.
> (enable this if your drive has lots of read errors, the access would be very
> slow)
> ++
> -f::::
> force using and overwriting <targetdev> even if it looks like
> containing a valid btrfs filesystem.
> @@ -49,6 +50,7 @@ containing a valid btrfs filesystem.
> A valid filesystem is assumed if a btrfs superblock is found which contains a
> correct checksum. Devices which are currently mounted are
> never allowed to be used as the <targetdev>.
> ++
> -B::::
> no background replace.
>
>
prev parent reply other threads:[~2014-08-07 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 7:28 [PATCH] btrfs-progs: Documentations: Fix a format error in btrfs-replace.txt Qu Wenruo
2014-08-07 10:25 ` Satoru Takeuchi [this message]
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=53E35430.9070408@jp.fujitsu.com \
--to=takeuchi_satoru@jp.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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 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.