Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Michael Waite <mwaite@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: KVM for the enterprise
Date: Sat, 19 Nov 2011 04:54:29 -0500	[thread overview]
Message-ID: <20111119095428.GA21458@infradead.org> (raw)
In-Reply-To: <4EC68702.3060804@redhat.com>

On Fri, Nov 18, 2011 at 11:25:38AM -0500, Michael Waite wrote:
>  Hi,
> The Open Virtualization Alliance is going to be having a webinar on
> December 8th which is intended to help promote KVM as an enterprise
> class hypervisor. I see so much great engineering work going on to
> make KVM a really robust technology and we want to help tell this
> story to the world-wide audience.

Maybe it's time to create a kvm-marketing@whatever list for sneaky
marketing BS from people like you instead of spamming development lists
like this one?


      reply	other threads:[~2011-11-19  9:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 16:25 KVM for the enterprise Michael Waite
2011-11-19  9:54 ` Christoph Hellwig [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=20111119095428.GA21458@infradead.org \
    --to=hch@infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=mwaite@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