public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: David Teigland <teigland@fedoraproject.org>
To: cluster-cvs-relay@redhat.com
Subject: cluster: STABLE3 - cluster.rng: remove trailing whitespace
Date: Mon, 27 Jul 2009 21:14:00 -0000	[thread overview]
Message-ID: <20090727211419.18EDF120307@lists.fedorahosted.org> (raw)

Gitweb:        http://git.fedorahosted.org/git/cluster.git?p=cluster.git;a=commitdiff;h=4be2a85079cd05df9dd07b555f88ad0184d9f7a5
Commit:        4be2a85079cd05df9dd07b555f88ad0184d9f7a5
Parent:        0fd3604ad2ee638f86cfe2b33a7588158391a8e5
Author:        David Teigland <teigland@redhat.com>
AuthorDate:    Mon Jul 27 16:04:50 2009 -0500
Committer:     David Teigland <teigland@redhat.com>
CommitterDate: Mon Jul 27 16:04:50 2009 -0500

cluster.rng: remove trailing whitespace

Signed-off-by: David Teigland <teigland@redhat.com>
---
 config/tools/xml/cluster.rng |   22 +++++++++++-----------
 1 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/config/tools/xml/cluster.rng b/config/tools/xml/cluster.rng
index fe90dc9..1fb1b65 100644
--- a/config/tools/xml/cluster.rng
+++ b/config/tools/xml/cluster.rng
@@ -5,7 +5,7 @@ xmlns:rha="http://redhat.com/~pkennedy/annotation_namespace/cluster_conf_annot_n
 <!-- The cluster.conf schema follows this outline:
 
 cluster
-- cman 
+- cman
 - clusternodes
 - dlm
 - gfs_controld
@@ -20,7 +20,7 @@ cluster
 
 Element defnitions:
 - Resource
-- Fence	
+- Fence
 
 To validate your cluster.conf against this schema, run:
 
@@ -145,7 +145,7 @@ To validate your cluster.conf against this schema, run:
        </attribute>
        <optional>
 	 <attribute name="votes" rha:description="The number of votes a
-            node can cast" rha:sample="2" rha:default="1"> 
+            node can cast" rha:sample="2" rha:default="1">
 	   <data type="positiveInteger"/>
 	 </attribute>
        </optional>
@@ -307,9 +307,9 @@ To validate your cluster.conf against this schema, run:
   </optional>
  </element>
  </optional>
-<!-- end gfs_controld block --> 
+<!-- end gfs_controld block -->
 
-<!-- group block --> 
+<!-- group block -->
  <optional>
  <element name="group" rha:description="">
   <optional>
@@ -317,7 +317,7 @@ To validate your cluster.conf against this schema, run:
   </optional>
  </element>
  </optional>
-<!-- end group block --> 
+<!-- end group block -->
 
 <!--FIXME: The following text was copied from the schema description
 here:
@@ -358,11 +358,11 @@ offers one other feature for customizing fence action. Within a <method>
 block, it is allowable to list more than one <device>. This is useful
 when fencing a node with redundant power supplies, for example. The
 fence daemon will run the agent for each device listed within a <method>
-block before determining success or failure. 
+block before determining success or failure.
 -->
 
 <!--fencedevices block-->
- 
+
  <optional>
  <element name="fencedevices" rha:description="This element and its
      attributes define the fence devices in the cluster. Parameters
@@ -1029,7 +1029,7 @@ block before determining success or failure.
       cluster services, the HA cluster services themselves, and failover
       domains for the HA cluster services.">
    <optional>
-    <!-- FIXME: The following text needs clarifying. What is meant by 
+    <!-- FIXME: The following text needs clarifying. What is meant by
     "...for all levels less than the selected."? -->
     <attribute name="log_level" rha:description="An integer 0-7,
         inclusive, for all levels less than the selected.
@@ -1162,7 +1162,7 @@ block before determining success or failure.
      </zeroOrMore>
     </element>
    </optional>  <!-- End of events block -->
-   <optional> 
+   <optional>
     <element name="resources" rha:description="">
      <zeroOrMore>
       <ref name="CHILDREN"/>
@@ -2783,4 +2783,4 @@ rha:sample=""/>
        </choice>
       </element>
      </define>
-</grammar>      
+</grammar>


                 reply	other threads:[~2009-07-27 21:14 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=20090727211419.18EDF120307@lists.fedorahosted.org \
    --to=teigland@fedoraproject.org \
    --cc=cluster-cvs-relay@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).