From: rmccabe@sourceware.org <rmccabe@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] conga ./clustermon.spec.in.in make/version.in
Date: 2 Jan 2008 22:45:33 -0000 [thread overview]
Message-ID: <20080102224533.13809.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: conga
Branch: RHEL4
Changes by: rmccabe at sourceware.org 2008-01-02 22:45:33
Modified files:
. : clustermon.spec.in.in
make : version.in
Log message:
fix 426189: Conga attempts to free a null pointer
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/clustermon.spec.in.in.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.25.2.9&r2=1.25.2.10
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/make/version.in.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.28.2.8&r2=1.28.2.9
--- conga/clustermon.spec.in.in 2007/11/02 05:44:33 1.25.2.9
+++ conga/clustermon.spec.in.in 2008/01/02 22:45:31 1.25.2.10
@@ -195,6 +195,10 @@
%changelog
+* Wed Jan 02 2008 Ryan McCabe <rmccabe@redhat.com> 0.11.0-4
+- Fix bz426189 (Conga attempts to free a null pointer)
+- Resolves: bz426189
+
* Mon Oct 22 2007 Ryan McCabe <rmccabe@redhat.com> 0.11.0-3
- Fix bz334441 (Can't get cluster-snmp (fully) working)
- Resolves: bz334441
--- conga/make/version.in 2007/10/20 01:49:39 1.28.2.8
+++ conga/make/version.in 2008/01/02 22:45:33 1.28.2.9
@@ -1,5 +1,5 @@
VERSION=0.11.0
-RELEASE=3
+RELEASE=4
# Remove "_UNRELEASED" at release time.
# Put release num at the beggining,
# so that after it gets released, it has
next reply other threads:[~2008-01-02 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 22:45 rmccabe [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-28 1:15 [Cluster-devel] conga ./clustermon.spec.in.in make/version.in rmccabe
2008-01-21 23:17 rmccabe
2007-12-06 3:03 rmccabe
2007-12-04 21:13 rmccabe
2006-08-17 19:12 kupcevic
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=20080102224533.13809.qmail@sourceware.org \
--to=rmccabe@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).