cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: jparsons@sourceware.org <jparsons@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] conga/luci/site/luci/Extensions conga_constants.py
Date: 10 Oct 2006 21:26:01 -0000	[thread overview]
Message-ID: <20061010212601.4217.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	conga
Changes by:	jparsons at sourceware.org	2006-10-10 21:26:01

Modified files:
	luci/site/luci/Extensions: conga_constants.py 

Log message:
	fine tune error strings

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/luci/site/luci/Extensions/conga_constants.py.diff?cvsroot=cluster&r1=1.11&r2=1.12

--- conga/luci/site/luci/Extensions/conga_constants.py	2006/10/10 21:18:34	1.11
+++ conga/luci/site/luci/Extensions/conga_constants.py	2006/10/10 21:26:01	1.12
@@ -77,4 +77,4 @@
 START_NODE=4
 
 #cluster/node create error messages
-CLUNODE_CREATE_ERRORS = ["An unknown error occurred when creating this node", "A problem occurred when installing packages","A problem occurred when rebooting this node", "A problem occurred when propagating the configuration to this node", "A problem occurred when starting this node"]
+CLUNODE_CREATE_ERRORS = ["An unknown error occurred when creating this node: ", "A problem occurred when installing packages: ","A problem occurred when rebooting this node: ", "A problem occurred when propagating the configuration to this node: ", "A problem occurred when starting this node: "]



             reply	other threads:[~2006-10-10 21:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 21:26 jparsons [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-05  5:39 [Cluster-devel] conga/luci/site/luci/Extensions conga_constants.py rmccabe
2007-06-05  5:37 rmccabe
2006-12-21  3:42 rmccabe
2006-11-27 20:06 rmccabe
2006-10-10 21:18 jparsons
2006-08-13 14:02 jparsons
2006-07-25  2:28 jparsons
2006-07-14 16:48 jparsons

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=20061010212601.4217.qmail@sourceware.org \
    --to=jparsons@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).