All of lore.kernel.org
 help / color / mirror / Atom feed
From: kupcevic@sourceware.org <kupcevic@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] conga ./conga.spec.in.in ./clustermon.spec.in. ...
Date: 17 Nov 2006 20:12:02 -0000	[thread overview]
Message-ID: <20061117201202.20576.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	conga
Changes by:	kupcevic at sourceware.org	2006-11-17 20:12:01

Modified files:
	.              : conga.spec.in.in clustermon.spec.in.in 
	make           : version.in 

Log message:
	version 0.9.1-1

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/conga.spec.in.in.diff?cvsroot=cluster&r1=1.52&r2=1.53
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/clustermon.spec.in.in.diff?cvsroot=cluster&r1=1.22&r2=1.23
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/make/version.in.diff?cvsroot=cluster&r1=1.26&r2=1.27

--- conga/conga.spec.in.in	2006/11/16 18:23:55	1.52
+++ conga/conga.spec.in.in	2006/11/17 20:12:00	1.53
@@ -283,12 +283,7 @@
 
 %changelog
 
-* Wed Nov 15 2006 Stanko Kupcevic <kupcevic@redhat.com> 0.9.1-UNRELEASED_0
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-XXXXXXXXXXXXXXXXXXX UPDATE NOT RELEASED YET XXXXXXXXXXXXXXXXXXX
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
+* Fri Nov 17 2006 Stanko Kupcevic <kupcevic@redhat.com> 0.9.1-1
 - Fixed bz212440 (luci persists possibly incorrect name for a system)
 - Fixed bz215039 (Cannot create a new resource via luci web app)
 - Fixed bz215034 (Cannot change daemon properties via luci web app)
@@ -308,12 +303,6 @@
 - Storage module: properly probe cluster quorum if LVM locking 
   is marked as clustered
 
-- #Resolves: bz212440, bz215039, bz215034, bz214790, bz213690, bz213266
-- #Resolves: bz213083, bz212601, bz212021, bz212006, bz212584
-- #Related: bz213306
-
-
-
 * Wed Nov 01 2006 Stanko Kupcevic <kupcevic@redhat.com> 0.8-23
 - 213504: luci does not correctly handle cluster.conf with 
   nodes lacking FQDN
--- conga/clustermon.spec.in.in	2006/11/15 17:46:41	1.22
+++ conga/clustermon.spec.in.in	2006/11/17 20:12:00	1.23
@@ -195,15 +195,9 @@
 
 %changelog
 
-* Wed Nov 15 2006 Stanko Kupcevic <kupcevic@redhat.com> 0.9.1-UNRELEASED_0
-
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-XXXXXXXXXXXXXXXXXXX UPDATE NOT RELEASED YET XXXXXXXXXXXXXXXXXXX
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
+* Fri Nov 17 2006 Stanko Kupcevic <kupcevic@redhat.com> 0.9.1-1
  - version bump
 
-
 * Wed Nov 01 2006 Stanko Kupcevic <kupcevic@redhat.com> 0.8-23
 - version bump
 
--- conga/make/version.in	2006/11/15 17:46:42	1.26
+++ conga/make/version.in	2006/11/17 20:12:01	1.27
@@ -1,5 +1,6 @@
 VERSION=0.9.1
-RELEASE=UNRELEASED_0
+RELEASE=1
+#RELEASE=UNRELEASED_2
 # Remove "UNRELEASED_" at release time.
 # Put release num at the end, 
 # so that after it gets released, it has 



             reply	other threads:[~2006-11-17 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 20:12 kupcevic [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-20  5:36 [Cluster-devel] conga ./conga.spec.in.in ./clustermon.spec.in. rmccabe
2007-03-30 15:12 kupcevic
2007-03-21 16:55 kupcevic
2007-03-20 18:17 kupcevic
2006-11-17 20:39 kupcevic
2006-11-15 17:46 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=20061117201202.20576.qmail@sourceware.org \
    --to=kupcevic@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.