From: lhh@sourceware.org <lhh@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, master, updated. cluster-2.99.05-22-ga006cbd
Date: 26 Jun 2008 15:56:40 -0000 [thread overview]
Message-ID: <20080626155640.32648.qmail@sourceware.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".
http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=a006cbd31804652e23ab5dde423b2b2e7fa03f76
The branch, master has been updated
via a006cbd31804652e23ab5dde423b2b2e7fa03f76 (commit)
via fe771387a087c01f2867005cef4c445050b93472 (commit)
from beeb2070953548ecf38751294e5371a668f73ee2 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit a006cbd31804652e23ab5dde423b2b2e7fa03f76
Author: Lon Hohberger <lhh@redhat.com>
Date: Thu Jun 26 11:56:35 2008 -0400
[fence] fence_xvmd: Add KVM support; misc cleanups.
* WARNING WARNING WARNING: Changes the default URI to
KVM. You must specify uri="xen:///" in cluster.conf
to use Xen now (or -U xen:/// on the command line)
* fence_xvmd -h now displays appropriate cluster.conf
related help information.
* This commit simply fixes authorship of the previous
patch; apparently git lets you commit as root even
if a different user checked it out...
commit fe771387a087c01f2867005cef4c445050b93472
Author: Lon Hohberger <lhh@redhat.com>
Date: Thu Jun 26 11:53:44 2008 -0400
Revert "[fence] fence_xvmd: Add KVM support; misc cleanups."
This reverts commit beeb2070953548ecf38751294e5371a668f73ee2.
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
Cluster Project
reply other threads:[~2008-06-26 15:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080626155640.32648.qmail@sourceware.org \
--to=lhh@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).