From: Wols Lists <antlists@youngman.org.uk>
To: Jes Sorensen <jes.sorensen@gmail.com>, Zhilong Liu <zlliu@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/2] mdadm/manpage:update description for readonly in manpage
Date: Tue, 11 Apr 2017 17:30:25 +0100 [thread overview]
Message-ID: <58ED04A1.4010508@youngman.org.uk> (raw)
In-Reply-To: <6afe1397-3063-c5d7-58ba-f3dbdfa05336@gmail.com>
On 11/04/17 15:51, Jes Sorensen wrote:
>>
>> .TP
>> .B \-\-readonly
>> -This will mark an active array as read-only, providing that it is
>> -not currently being used.
>> +This will set an active array as read-only status.
>
> I think this chance is not good, and should be omitted.
Agreed, except that I would change "providing" to "provided".
>
>> .TP
>> .B \-\-readwrite
>> -This will change a
>> +This will change an
>> .B readonly
>> array back to being read/write.
>
> This change is grammatically incorrect I believe and the original text
> is correct.
Agreed.
Cheers,
Wol
next prev parent reply other threads:[~2017-04-11 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 8:01 [PATCH 0/2] mdadm/manpage: update manpage for readonly and array-size Zhilong Liu
2017-04-10 8:04 ` [PATCH 1/2] mdadm/manpage:update description for readonly in manpage Zhilong Liu
2017-04-10 8:04 ` [PATCH 2/2] mdadm/manpage:clustered array doesn't support --array-size yet Zhilong Liu
2017-04-11 14:49 ` Jes Sorensen
2017-04-12 8:37 ` [PATCH v1 2/2] mdadm/manpage:clustered arrays don't support array-size yet Zhilong Liu
2017-04-12 17:57 ` Jes Sorensen
2017-04-11 14:51 ` [PATCH 1/2] mdadm/manpage:update description for readonly in manpage Jes Sorensen
2017-04-11 16:30 ` Wols Lists [this message]
2017-04-12 8:36 ` [PATCH v1 1/2] mdadm/manpage:update manpage for readonly parameter Zhilong Liu
2017-04-12 17:51 ` Jes Sorensen
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=58ED04A1.4010508@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=zlliu@suse.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 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).