From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs2/man gfs2_jadd.8
Date: 24 Oct 2007 21:19:49 -0000 [thread overview]
Message-ID: <20071024211949.28189.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: rpeterso at sourceware.org 2007-10-24 21:19:48
Modified files:
gfs2/man : gfs2_jadd.8
Log message:
Resolves: bug #334481: gfs2_jadd man page refers to non-existent -T option
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/man/gfs2_jadd.8.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.1&r2=1.1.2.1
--- cluster/gfs2/man/gfs2_jadd.8 2005/05/24 22:16:15 1.1
+++ cluster/gfs2/man/gfs2_jadd.8 2007/10/24 21:19:48 1.1.2.1
@@ -30,9 +30,6 @@
mounted filesystem and so failure part way through the expansion
process should leave your filesystem in its original state.
-You can run \fIgfs2_jadd\fR with the \fI-T\fR flag to get a display
-of the current state of a mounted GFS2 filesystem.
-
.SH OPTIONS
.TP
\fB-c MegaBytes\fP
@@ -56,11 +53,6 @@
\fB-q\fP
Be quiet. Don't print anything.
.TP
-\fB-T\fP
-Test. Do all calculations, but do not write any data to the disk and do
-not add journals. This is used to discover what the tool would
-have done were it run without this flag.
-.TP
\fB-u MegaBytes\fP
Initial size of each journal's unlinked tag file
.TP
next reply other threads:[~2007-10-24 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 21:19 rpeterso [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-24 21:19 [Cluster-devel] cluster/gfs2/man gfs2_jadd.8 rpeterso
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=20071024211949.28189.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).