From: Marek Grac <mgrac@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 1/3] New fencing script for Citrix XenServer and XCP.
Date: Fri, 15 Apr 2011 10:02:28 +0200 [thread overview]
Message-ID: <4DA7FB94.6010600@redhat.com> (raw)
In-Reply-To: <4DA3CF62.6000807@redhat.com>
Hi,
On 04/12/2011 06:04 AM, Fabio M. Di Nitto wrote:
>> Your
>> comments all sound perfectly valid. Do you want me to fix up and resubmit?
> Let's wait for Marek feedback first and keep the changes local in the
> meantime. The build bits are easy to fix on the fly anyway.
Fence agent looks fine for me, Matt fixed my objections before.
m,
next prev parent reply other threads:[~2011-04-15 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-09 4:54 [Cluster-devel] [PATCH 1/3] New fencing script for Citrix XenServer and XCP Matt Clark
2011-04-09 4:54 ` [Cluster-devel] [PATCH 2/3] Updated to include xenapi script Matt Clark
2011-04-09 4:54 ` [Cluster-devel] [PATCH 3/3] Updated to include xenapi script in Makefile.am Matt Clark
2011-04-11 5:01 ` [Cluster-devel] [PATCH 1/3] New fencing script for Citrix XenServer and XCP Fabio M. Di Nitto
2011-04-12 2:46 ` Matt Clark
2011-04-12 4:04 ` Fabio M. Di Nitto
2011-04-15 8:02 ` Marek Grac [this message]
2011-04-15 8:13 ` Fabio M. Di Nitto
2011-04-17 7:44 ` Matt Clark
2011-04-17 12:09 ` Fabio M. Di Nitto
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=4DA7FB94.6010600@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).