From: rmccabe@sourceware.org <rmccabe@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] conga/luci/site/luci/Extensions ricci_communic ...
Date: 20 Oct 2006 18:37:50 -0000 [thread overview]
Message-ID: <20061020183750.12254.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: conga
Changes by: rmccabe at sourceware.org 2006-10-20 18:37:50
Modified files:
luci/site/luci/Extensions: ricci_communicator.py
Log message:
duh. some kind of cut and paste error, i guess.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/luci/site/luci/Extensions/ricci_communicator.py.diff?cvsroot=cluster&r1=1.10&r2=1.11
--- conga/luci/site/luci/Extensions/ricci_communicator.py 2006/10/18 21:59:47 1.10
+++ conga/luci/site/luci/Extensions/ricci_communicator.py 2006/10/20 18:37:50 1.11
@@ -16,8 +16,7 @@
pass
class RicciError(Exception):
- def __init__(self, e):
- pass
+ pass
class RicciCommunicator:
def __init__(self, hostname, port=11111):
next reply other threads:[~2006-10-20 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 18:37 rmccabe [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-26 4:23 [Cluster-devel] conga/luci/site/luci/Extensions ricci_communic rmccabe
2007-07-03 16:56 rmccabe
2006-10-10 21:07 kupcevic
2006-09-26 21:04 kupcevic
2006-06-21 23:07 rmccabe
2006-06-19 17:10 rmccabe
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=20061020183750.12254.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).