From: Andrea Gelmini <andrea.gelmini@gelma.net>
To: linux-btrfs@vger.kernel.org
Cc: lizf@cn.fujitsu.com, Andrea Gelmini <andrea.gelmini@gelma.net>
Subject: [PATCH] Btrfs-progs: man: fix typo
Date: Wed, 22 Feb 2012 13:47:27 +0100 [thread overview]
Message-ID: <1329914848-5698-1-git-send-email-andrea.gelmini@gelma.net> (raw)
s/eveery/every/
Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
man/btrfs.8.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/btrfs.8.in b/man/btrfs.8.in
index 8e3b2f5..e2792c9 100644
--- a/man/btrfs.8.in
+++ b/man/btrfs.8.in
@@ -137,7 +137,7 @@ is similar to \fBsubvolume list\fR command.
Defragment file data and/or directory metadata. To defragment all files in a
directory you have to specify each one on its own or use your shell wildcards.
-The start position and the number of bytes to deframention can be specified by \fIstart\fR and \fIlen\fR. Any extent bigger than \fIthresh\fR will be considered already defragged. Use 0 to take the kernel default, and use 1 to say eveery single extent must be rewritten. You can also turn on compression in defragment operations.
+The start position and the number of bytes to deframention can be specified by \fIstart\fR and \fIlen\fR. Any extent bigger than \fIthresh\fR will be considered already defragged. Use 0 to take the kernel default, and use 1 to say every single extent must be rewritten. You can also turn on compression in defragment operations.
\fB-v\fP be verbose
--
1.7.9.1.275.gd59d2
reply other threads:[~2012-02-22 12:47 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=1329914848-5698-1-git-send-email-andrea.gelmini@gelma.net \
--to=andrea.gelmini@gelma.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@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 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).