From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Changes to fencing.py
Date: Tue, 22 Mar 2011 15:19:23 -0400 [thread overview]
Message-ID: <20110322191923.GF20517@redhat.com> (raw)
In-Reply-To: <col108-w437FE5346B960746FA7D5DDB40@phx.gbl>
On Tue, Mar 22, 2011 at 11:14:07AM +1100, Matt Clark wrote:
>
> Hi,
> I sent an email a little while about a fencing agent script I was writing to handle Citrix XenServer virtual machine (and apparently XCP virtual machine). I think I am pretty close to finishing this off as I haven't made any code changes in a few weeks. Usually a good sign it's at least ready for others to test/play with.
> I had to make the following changes to the fencing library. Feedback welcome.
> Script source (fence_cxs_redhat.py) available athttp://code.google.com/p/fence-xenserver/downloads/list
> Thanks,
> Matt.
Your patch formatted on one line for some reason; can you just do a 'git
send-email' on your patch to resend it?
--
Lon Hohberger - Red Hat, Inc.
prev parent reply other threads:[~2011-03-22 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 0:14 [Cluster-devel] Changes to fencing.py Matt Clark
2011-03-22 19:19 ` Lon Hohberger [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=20110322191923.GF20517@redhat.com \
--to=lhh@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).