From: lhh@sourceware.org <lhh@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, master, updated. cluster-2.99.02-20-gb97ae81
Date: 22 May 2008 14:33:20 -0000 [thread overview]
Message-ID: <20080522143320.7631.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=b97ae81d1aa7ae7be15f02852bd21184b9e2570f
The branch, master has been updated
via b97ae81d1aa7ae7be15f02852bd21184b9e2570f (commit)
from dfa234e63d2be04efafbdd8c1d8e8340a8b27b1b (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 b97ae81d1aa7ae7be15f02852bd21184b9e2570f
Author: Lon Hohberger <lhh@redhat.com>
Date: Thu May 22 10:33:12 2008 -0400
[rgmanager] Use /cluster/rm instead of //rm
* It is more efficient
* It is a well-defined location
-----------------------------------------------------------------------
Summary of changes:
rgmanager/include/reslist.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/rgmanager/include/reslist.h b/rgmanager/include/reslist.h
index 4efe879..219386b 100644
--- a/rgmanager/include/reslist.h
+++ b/rgmanager/include/reslist.h
@@ -57,7 +57,7 @@
#endif
#define RESOURCE_ROOTDIR SHAREDIR
-#define RESOURCE_TREE_ROOT "//rm"
+#define RESOURCE_TREE_ROOT "/cluster/rm"
#define RESOURCE_BASE RESOURCE_TREE_ROOT "/resources"
#define RESOURCE_ROOT_FMT RESOURCE_TREE_ROOT "/%s[%d]"
hooks/post-receive
--
Cluster Project
reply other threads:[~2008-05-22 14:33 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=20080522143320.7631.qmail@sourceware.org \
--to=lhh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.