mke2fs.8: use extents vs extent in the man page

We print "extents" for the feature, so we should document "extents" in
the mke2fs's man page, even though we accept both "extent" and
"extents".

Addresses-Sourceforge-Bug: #3559210

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>

diff --git a/misc/mke2fs.8.in b/misc/mke2fs.8.in
index 6d443a2ac53df08b106335227c91be2a26b6f453..d4fbe00cea9ab1c07be772bb8c5e1e7b1313c714 100644 (file)
--- a/misc/mke2fs.8.in
+++ b/misc/mke2fs.8.in
@@ -519,11 +519,12 @@ pseudo-filesystem feature "none" will clear all filesystem features.
 .B dir_index
 Use hashed b-trees to speed up lookups in large directories.
 .TP
-.B extent
+.B extents
 Instead of using the indirect block scheme for storing the location of
 data blocks in an inode, use extents instead.  This is a much more
 efficient encoding which speeds up filesystem access, especially for
-large files.
+large files.  (Note: both extent and extents are accepted for
+historical/backwards compatibility reasons.)
 .TP
 .B filetype
 Store file type information in directory entries.