From: Marek Grac <mgrac@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Use exceptions not strings in 'raise'
Date: Fri, 09 Jul 2010 13:45:25 +0200 [thread overview]
Message-ID: <4C370BD5.6050100@redhat.com> (raw)
In-Reply-To: <4C31BBD2.9070107@redhat.com>
Hi,
On 07/05/2010 01:02 PM, Fabio M. Di Nitto wrote:
> On 7/2/2010 1:47 PM, Guido G?nther wrote:
>
>> Hi,
>> attached patch raises expceptions instead of strings in fence_rsb.py so
>> python 2.6 doesn't complain.
>>
> Marek,
>
> can you please ACK/NACK and commit in case?
>
>
Guido thanks for problem description and patch.
I have created a bug rhbz#612941
<https://bugzilla.redhat.com/show_bug.cgi?id=612941> and posted this
patch to upstream git.
Thanks
m,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20100709/579ffb8e/attachment.htm>
prev parent reply other threads:[~2010-07-09 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100702114750.GA8456@bogon.sigxcpu.org>
2010-07-05 11:02 ` [Cluster-devel] [PATCH] Use exceptions not strings in 'raise' Fabio M. Di Nitto
2010-07-09 11:41 ` Fabio M. Di Nitto
2010-07-09 11:45 ` Marek Grac [this message]
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=4C370BD5.6050100@redhat.com \
--to=mgrac@redhat.com \
/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).