public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: fabbione@sourceware.org
To: cluster-cvs@sources.redhat.com, cluster-devel@redhat.com
Subject: Cluster Project branch, STABLE2, updated. cluster-2.03.01-13-gc58f0a4
Date: Wed, 23 Apr 2008 10:24:00 -0000	[thread overview]
Message-ID: <20080423102449.27089.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=c58f0a46f6b06b0cf0b09dad2c3114fe5742a489

The branch, STABLE2 has been updated
       via  c58f0a46f6b06b0cf0b09dad2c3114fe5742a489 (commit)
      from  23d5682698c2de24f29037c3a8081740a0419668 (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 c58f0a46f6b06b0cf0b09dad2c3114fe5742a489
Author: Jonathan Brassow <jbrassow@redhat.com>
Date:   Tue Apr 22 13:56:52 2008 -0500

    rgmanager/lvm.metadata: Fix parameter description fields
    
    Descriptions were never properly updated after creation.

-----------------------------------------------------------------------

Summary of changes:
 rgmanager/src/resources/lvm.metadata |   12 +++++++-----
 1 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/rgmanager/src/resources/lvm.metadata b/rgmanager/src/resources/lvm.metadata
index 650675b..fdf2621 100755
--- a/rgmanager/src/resources/lvm.metadata
+++ b/rgmanager/src/resources/lvm.metadata
@@ -13,7 +13,7 @@
     <parameters>
         <parameter name="name" primary="1">
             <longdesc lang="en">
-                Descriptive name LVM Volume group
+                Unique name for this LVM resource
             </longdesc>
             <shortdesc lang="en">
                 Name
@@ -23,20 +23,22 @@
 
         <parameter name="vg_name" required="1">
             <longdesc lang="en">
-                If you can see this, your GUI is broken.
+                Name of the volume group being managed
             </longdesc>
             <shortdesc lang="en">
-                If you can see this, your GUI is broken.
+                Volume group name
             </shortdesc>
 	    <content type="string"/>
         </parameter>
 
         <parameter name="lv_name">
             <longdesc lang="en">
-                If you can see this, your GUI is broken.
+                Name of the logical volume being managed.  This
+		parameter is optional if there are more than one
+		logical volumes in the volume group to be managed.
             </longdesc>
             <shortdesc lang="en">
-                If you can see this, your GUI is broken.
+                Logical Volume name (optional).
             </shortdesc>
 	    <content type="string"/>
 	</parameter>


hooks/post-receive
--
Cluster Project


                 reply	other threads:[~2008-04-23 10:24 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=20080423102449.27089.qmail@sourceware.org \
    --to=fabbione@sourceware.org \
    --cc=cluster-cvs@sources.redhat.com \
    --cc=cluster-devel@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).