From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [fence-virt PATCH] fix handling of VIR_DOMAIN_EVENT_STARTED
Date: Tue, 07 Feb 2012 18:17:42 -0500 [thread overview]
Message-ID: <4F31B116.3030706@redhat.com> (raw)
In-Reply-To: <4E6F1809.8020300@intellilink.co.jp>
On 09/13/2011 04:44 AM, Kazunori INOUE wrote:
[all late and wrong]
Merged in to 0.3.0
-- Lon
prev parent reply other threads:[~2012-02-07 23:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 8:44 [Cluster-devel] [fence-virt PATCH] fix handling of VIR_DOMAIN_EVENT_STARTED Kazunori INOUE
2011-09-19 20:32 ` Lon Hohberger
2011-10-25 23:30 ` Lon Hohberger
2011-10-27 7:23 ` Kazunori INOUE
2011-11-22 9:31 ` Kazunori INOUE
2012-02-07 23:17 ` 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=4F31B116.3030706@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).