All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: xfs-oss <xfs@oss.sgi.com>, linux-xfs@vger.kernel.org
Cc: Chris Murphy <chris@cmurf.com>
Subject: [PATCH] mkfs.xfs: clarify ftype defaults in manpage
Date: Fri, 16 Sep 2016 15:48:14 -0500	[thread overview]
Message-ID: <1f98ea1d-893c-d1c0-2307-3f5a9b478238@redhat.com> (raw)

When CRCs were made default, a few leftovers related to its
prior non-default status remained in the manpage, in the ftype
section.  Clean those up.

Reported-by: Chris Murphy <chris@cmurf.com>
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---

diff --git a/man/man8/mkfs.xfs.8 b/man/man8/mkfs.xfs.8
index 9578c4d..033bc36 100644
--- a/man/man8/mkfs.xfs.8
+++ b/man/man8/mkfs.xfs.8
@@ -636,13 +636,13 @@ do not need to look up the inode to determine the inode type.
 
 The
 .I value
-is either 0 or 1, with 1 signifiying that filetype information
-will be stored in the directory structure. The default value is 0.
+is either 0 or 1, with 1 signifying that filetype information
+will be stored in the directory structure.
 
-When CRCs are enabled via
-.B \-m crc=1,
-the ftype functionality is always enabled. This feature can not be turned
-off for such filesystem configurations.
+When CRCs are enabled (the default), the ftype functionality is always
+enabled, and cannot be turned off. If CRCs are disabled with
+.B \-m crc=0,
+the ftype functionality is disabled by default.
 .IP
 .RE
 .TP



             reply	other threads:[~2016-09-16 20:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16 20:48 Eric Sandeen [this message]
2016-09-19  2:16 ` [PATCH] mkfs.xfs: clarify ftype defaults in manpage Dave Chinner
2016-09-19 12:44   ` Eric Sandeen
2016-09-19 13:26 ` [PATCH V2] " Eric Sandeen
2016-09-25 14:35   ` Christoph Hellwig

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=1f98ea1d-893c-d1c0-2307-3f5a9b478238@redhat.com \
    --to=sandeen@redhat.com \
    --cc=chris@cmurf.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.