From: Wieland Hoffmann <themineo@gmail.com>
To: linux-raid@vger.kernel.org
Subject: [PATCH] mdadm.8.in: Fix typo: previous -> previously
Date: Sat, 9 Mar 2013 15:34:24 +0100 [thread overview]
Message-ID: <1362839664-361-1-git-send-email-themineo@gmail.com> (raw)
Signed-off-by: Wieland Hoffmann <themineo@gmail.com>
---
mdadm.8.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mdadm.8.in b/mdadm.8.in
index 1c06533..f7aa6aa 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -1224,7 +1224,7 @@ with redundancy. They don't apply to RAID0 or Linear.
.TP
.BR \-\-re\-add
-re\-add a device that was previous removed from an array.
+re\-add a device that was previously removed from an array.
If the metadata on the device reports that it is a member of the
array, and the slot that it used is still vacant, then the device will
be added back to the array in the same position. This will normally
--
1.8.1.5
next reply other threads:[~2013-03-09 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 14:34 Wieland Hoffmann [this message]
2013-03-10 9:31 ` [PATCH] mdadm.8.in: Fix typo: previous -> previously Paul Menzel
2013-07-01 13:13 ` Wieland Hoffmann
2013-07-01 22:32 ` NeilBrown
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=1362839664-361-1-git-send-email-themineo@gmail.com \
--to=themineo@gmail.com \
--cc=linux-raid@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).