From: lhh@sourceware.org <lhh@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/rgmanager ChangeLog
Date: 6 Oct 2006 21:23:40 -0000 [thread overview]
Message-ID: <20061006212340.11727.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: lhh at sourceware.org 2006-10-06 21:23:40
Modified files:
rgmanager : ChangeLog
Log message:
Fixed 202492, not 202497...
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/rgmanager/ChangeLog.diff?cvsroot=cluster&r1=1.28&r2=1.29
--- cluster/rgmanager/ChangeLog 2006/10/06 21:22:27 1.28
+++ cluster/rgmanager/ChangeLog 2006/10/06 21:23:40 1.29
@@ -1,11 +1,11 @@
2006-10-06 Lon Hohberger <lhh@redhat.com>
- * src/daemons/main.c: Fix #202497: provide rgmanager's view of
+ * src/daemons/main.c: Fix #202492: provide rgmanager's view of
who is running rgmanager to clustat.
* src/daemons/groups.c: Fix tiny memory leak during configuration
changes
- * include/resgroup.h: #202497: Flip unused RG_STATUS_INQUIRY to
+ * include/resgroup.h: #202492: Flip unused RG_STATUS_INQUIRY to
RG_STATUS_NODE.
- * src/utils/clustat.c: #202497: Send RG_STATUS_NODE to clurgmgrd
+ * src/utils/clustat.c: #202492: Send RG_STATUS_NODE to clurgmgrd
in order to obtain rgmanager "group" status information
2006-09-27 Lon Hohberger <lhh@redhat.com>
next reply other threads:[~2006-10-06 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 21:23 lhh [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-25 15:39 [Cluster-devel] cluster/rgmanager ChangeLog lhh
2007-04-19 20:21 lhh
2007-05-10 16:26 lhh
2007-05-22 17:01 lhh
2007-05-22 17:02 lhh
2007-05-31 18:38 lhh
2007-10-26 20:27 lhh
2007-11-26 21:37 lhh
2007-11-30 19:47 lhh
2007-12-19 21:34 lhh
2008-01-28 19:42 lhh
2008-02-01 15:17 lhh
2008-02-05 19:50 lhh
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=20061006212340.11727.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 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).