From: Brett Johnson <brett-VXdhtT5mjnY@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: KVM name?
Date: Fri, 10 Nov 2006 15:33:27 -0700 [thread overview]
Message-ID: <1163198007.31875.4.camel@jayne> (raw)
On 2006-11-10 02:35:00 GMT, Anthony Liguori wrote:
> This was bound to come up eventually, but perhaps KVM isn't the best
> name since it's overloading a rather commonly used acronym.
How about "XINXEN"? (Xinxen Is Not XEN ;o)
--
Brett Johnson <brett-VXdhtT5mjnY@public.gmane.org>
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-11-10 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 22:33 Brett Johnson [this message]
2006-11-10 22:47 ` KVM name? Brett Johnson
-- strict thread matches above, loose matches on Subject: below --
2006-11-10 2:35 Anthony Liguori
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=1163198007.31875.4.camel@jayne \
--to=brett-vxdhtt5mjny@public.gmane.org \
--cc=brett-+nN6oZZ19oAAvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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