From: Ming Zhang <mingz@ele.uri.edu>
To: linux-xfs <linux-xfs@oss.sgi.com>
Subject: [patch]typo
Date: Wed, 26 Jul 2006 09:06:57 -0400 [thread overview]
Message-ID: <1153919217.2658.8.camel@localhost.localdomain> (raw)
A typo in xfs_fsr man page.
Ming
--- xfs_fsr.8.old 2006-07-26 09:05:06.000000000 -0400
+++ xfs_fsr.8 2006-07-26 09:05:38.000000000 -0400
@@ -107,7 +107,7 @@
file to a temporary location and then interchanging the data extents
of the target and temporary files in an atomic manner.
This method requires that enough free disk space be available to copy
-any given file and that the space be less fragmented then the original
+any given file and that the space be less fragmented than the original
file.
It also requires the owner of the file to have enough remaining
filespace quota to do the copy on systems running quotas.
reply other threads:[~2006-07-26 13:07 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=1153919217.2658.8.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=linux-xfs@oss.sgi.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