public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] xfsprogs: remove xfs_check references from fsck.xfs script & manpage
Date: Tue, 12 Nov 2013 10:31:12 -0600	[thread overview]
Message-ID: <528257D0.7050404@redhat.com> (raw)

xfs_check is deprecated & slated for removal in June 2014.

We can stop referring to it now, though - pointing fsck.xfs
users to it doesn't make sense at this point.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---

diff --git a/fsck/xfs_fsck.sh b/fsck/xfs_fsck.sh
index c5a96e6..e52969e 100755
--- a/fsck/xfs_fsck.sh
+++ b/fsck/xfs_fsck.sh
@@ -19,6 +19,6 @@ if $AUTO; then
 	echo "$0: XFS file system."
 else
 	echo "If you wish to check the consistency of an XFS filesystem or"
-	echo "repair a damaged filesystem, see xfs_check(8) and xfs_repair(8)."
+	echo "repair a damaged filesystem, see xfs_repair(8)."
 fi
 exit 0
diff --git a/man/man8/fsck.xfs.8 b/man/man8/fsck.xfs.8
index b890ad1..ace7252 100644
--- a/man/man8/fsck.xfs.8
+++ b/man/man8/fsck.xfs.8
@@ -20,8 +20,6 @@ simply exits with a zero exit status.
 If you wish to check the consistency of an XFS filesystem,
 or repair a damaged or corrupt XFS filesystem,
 see
-.BR xfs_check (8)
-and
 .BR xfs_repair (8).
 .
 .SH FILES
@@ -30,5 +28,4 @@ and
 .BR fsck (8),
 .BR fstab (5),
 .BR xfs (5),
-.BR xfs_check (8),
 .BR xfs_repair (8).

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2013-11-12 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 16:31 Eric Sandeen [this message]
2013-11-12 17:38 ` [PATCH] xfsprogs: remove xfs_check references from fsck.xfs script & manpage Christoph Hellwig
2013-11-13  2:12 ` Rich Johnston

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=528257D0.7050404@redhat.com \
    --to=sandeen@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox