From: fabbione@sourceware.org <fabbione@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, STABLE2, updated. cluster-2.02.00-17-g1c5fcd3
Date: 16 Mar 2008 05:52:56 -0000 [thread overview]
Message-ID: <20080316055256.7778.qmail@sourceware.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".
http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=1c5fcd3e08369099f71182557cd88470860d2e85
The branch, STABLE2 has been updated
via 1c5fcd3e08369099f71182557cd88470860d2e85 (commit)
from 52bd5e962e13261a22aa984eec98439b0a59f0bb (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 1c5fcd3e08369099f71182557cd88470860d2e85
Author: Bob Peterson <rpeterso@redhat.com>
Date: Tue Mar 11 18:23:11 2008 -0500
Resolves: bz 435917: GFS2: mkfs.gfs2 default lock protocol
differs from man page
-----------------------------------------------------------------------
Summary of changes:
gfs2/man/mkfs.gfs2.8 | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/gfs2/man/mkfs.gfs2.8 b/gfs2/man/mkfs.gfs2.8
index c68ff8d..b411467 100644
--- a/gfs2/man/mkfs.gfs2.8
+++ b/gfs2/man/mkfs.gfs2.8
@@ -48,10 +48,10 @@ the filesystem.
.TP
\fB-p\fP \fILockProtoName\fR
LockProtoName is the name of the locking protocol to use. Acceptable
-locking protocols are \fIlock_dlm\fR or if you are using GFS2
-as a local filesystem (\fB1 node only\fP), you can specify the
+locking protocols are \fIlock_dlm\fR (for shared storage) or if you are
+using GFS2 as a local filesystem (\fB1 node only\fP), you can specify the
\fIlock_nolock\fR protocol. If this option is not specified,
-\fIlock_nolock\fR protocol will be assumed.
+\fIlock_dlm\fR protocol will be assumed.
.TP
\fB-q\fP
Be quiet. Don't print anything.
hooks/post-receive
--
Cluster Project
reply other threads:[~2008-03-16 5:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080316055256.7778.qmail@sourceware.org \
--to=fabbione@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).