cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs2/man gfs2_tool.8
Date: 9 Jan 2008 21:30:20 -0000	[thread overview]
Message-ID: <20080109213020.1429.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	rpeterso at sourceware.org	2008-01-09 21:30:20

Modified files:
	gfs2/man       : gfs2_tool.8 

Log message:
	Resolves: bz 426670: GFS2: man page for gfs2_tool has commented
	lockdump section

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/man/gfs2_tool.8.diff?cvsroot=cluster&r1=1.7&r2=1.8

--- cluster/gfs2/man/gfs2_tool.8	2007/11/14 17:18:09	1.7
+++ cluster/gfs2/man/gfs2_tool.8	2008/01/09 21:30:20	1.8
@@ -61,12 +61,10 @@
 represents the mounted filesystem. 2) The name of the
 device that holds the filesystem (well, the name as the Linux
 kernel knows it).
-.\".TP
-.\"\fBlockdump\fP \fIMountPoint\fR \fI[buffersize]\fR
-.\"Print out information about the locks this machine holds for a given
-.\"filesystem. Buffersize is the size of the buffer (in bytes) that gfs2_tool
-.\"allocates to store the lock data during processing.  It defaults to 4194304
-.\"bytes.
+.TP
+\fBlockdump\fP \fIMountPoint\fR
+Print out information about the locks this machine holds for a given
+filesystem.
 .\".TP
 .\"\fBmargs\fP \fIarguments\fR
 .\"This loads arguments into the module what will override the mount



             reply	other threads:[~2008-01-09 21:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09 21:30 rpeterso [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-09 21:30 [Cluster-devel] cluster/gfs2/man gfs2_tool.8 rpeterso
2007-11-07 21:15 rpeterso
2007-11-07 21:14 rpeterso
2007-07-26 23:22 rpeterso
2007-07-26 23:20 rpeterso
2007-07-26 23:19 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=20080109213020.1429.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).