From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs2/man gfs2.8
Date: 26 Jan 2008 14:20:58 -0000 [thread overview]
Message-ID: <20080126142058.28368.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: rpeterso at sourceware.org 2008-01-26 14:20:58
Modified files:
gfs2/man : gfs2.8
Log message:
Resolves: bz 223660: man gfs2(8) refers to the gfs2_mkfs manpage
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/man/gfs2.8.diff?cvsroot=cluster&r1=1.3&r2=1.4
--- cluster/gfs2/man/gfs2.8 2008/01/02 11:48:54 1.3
+++ cluster/gfs2/man/gfs2.8 2008/01/26 14:20:57 1.4
@@ -20,8 +20,11 @@
gfs2_mount
Mounting a GFS2 file system
.TP
+gfs2_edit
+A GFS2 debug tool (use with caution)
+.TP
gfs2_fsck
-The GFS2 file system checker (Still Missing)
+The GFS2 file system checker
.TP
gfs2_grow
Growing a GFS2 file system
@@ -29,7 +32,7 @@
gfs2_jadd
Adding a journal to a GFS2 file system
.TP
-gfs2_mkfs
+mkfs.gfs2
Make a GFS2 file system
.TP
gfs2_quota
next reply other threads:[~2008-01-26 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 14:20 rpeterso [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-19 20:11 [Cluster-devel] cluster/gfs2/man gfs2.8 cfeist
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=20080126142058.28368.qmail@sourceware.org \
--to=rpeterso@sourceware.org \
/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).