From: "Jeebs" <Jeebs@yango.us>
To: hetz@witch.dyndns.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu development schedule?
Date: Mon, 30 Aug 2004 17:59:29 -0500 [thread overview]
Message-ID: <002101c48ee5$46b2e280$20389c3f@computername> (raw)
In-Reply-To: 200408310107.07350.hetz@witch.dyndns.org
From: "Hetz Ben Hamo" <hetz@witch.dyndns.org>
>> Don't misunderstand me... The recent discussion about performance
>> improvements, and Fabrice's comments were *very* exciting.
>
> Indeed, but I would suggest to wait for some more info from Fabrice until
> he publishes somsthing..
Well, I'm not going to go and throw out my VMWare just yet, if that's what
you mean...[grin]
But it is very nice to see an open source project making such progress!
> Fabrice didn't do the Windows version port, someone else did it and I
> think
Right. I do know there are people in here besides him. It was just his
statement about the possible future performance that got me really excited.
> someone else is doing some front end for it (see my URL:
> http://dad-answers.com/qemu/patches for win32 stuff)
The only Windows front end I've seen was "Qemu Workstation" and that's
rather out of date and doesn't even work with the current daily FreeOSZoo
builds.
> QEMU is a "one man show" (fabrice) while some other contribute stuff for
That I didn't know.
I knew Fabrice was important, but wasn't aware that he was doing most of
the core stuff.
> committed to CVS - they might continue develop it or not, but with open
> source, someone else could possibly continue working on it..
Yup. That's one of the reasons I'd prefer an opensource product over
VMWare.
> other "sexy" stuff. For now - it's Fabrice "show" and others
> contributions....
>
> Hope it helps,
Thanks.
That does explain a few things.
So basically, there's no roadmap or schedule for features, etc. And it's
basically going to be a "free for all" for the foreseeable future.
next prev parent reply other threads:[~2004-08-30 23:06 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 21:44 [Qemu-devel] Qemu development schedule? Jeebs
2004-08-30 21:59 ` John R. Hogerhuis
2004-08-30 22:51 ` Jeebs
2004-08-31 11:59 ` Johannes Schindelin
2004-08-31 15:58 ` Jeebs
2004-08-31 16:27 ` Joe Batt
2004-08-31 17:42 ` Jeebs
2004-09-01 19:25 ` Kai Cherry
2004-09-01 19:33 ` andrej
2004-09-01 19:46 ` Joe Batt
2004-09-01 20:34 ` Mike Tremoulet
2004-09-01 20:46 ` Kai Cherry
2004-09-01 20:35 ` Kai Cherry
2004-09-02 20:46 ` Jim C. Brown
2004-09-03 7:52 ` [Qemu-devel] Filegetopt (Was: Qemu development schedule?) Renzo Davoli
2004-08-31 16:32 ` [Qemu-devel] Qemu development schedule? Johannes Schindelin
2004-08-31 17:40 ` Jeebs
2004-09-01 15:43 ` Lionel Ulmer
2004-09-01 17:03 ` John R. Hogerhuis
2004-09-01 19:07 ` Kai Cherry
2004-09-02 10:20 ` Info
2004-08-31 17:42 ` John R. Hogerhuis
2004-08-31 19:07 ` andrej
2004-08-31 19:44 ` Kai Cherry
2004-08-30 22:07 ` Hetz Ben Hamo
2004-08-30 22:59 ` Jeebs [this message]
2004-08-30 23:34 ` John R. Hogerhuis
2004-08-31 9:21 ` Kai Cherry
2004-08-31 10:15 ` Patrick Mauritz
2004-08-31 10:23 ` Kai Cherry
2004-08-31 17:23 ` Gianni Tedesco
2004-08-31 19:08 ` Kai Cherry
2004-09-01 20:53 ` Magnus Damm
2004-08-31 20:27 ` Fabrice Bellard
2004-08-31 21:50 ` René Korthaus
2004-09-01 22:04 ` Jim C. Brown
2004-08-31 22:02 ` Patrick Mauritz
2004-09-01 21:58 ` Jim C. Brown
2004-09-02 7:26 ` Lionel Ulmer
2004-09-02 20:56 ` Jim C. Brown
2004-09-02 23:28 ` Lionel Ulmer
2004-09-03 0:07 ` Jim C. Brown
2004-09-03 8:32 ` Fabrice Bellard
2004-09-03 7:29 ` Adrian Smarzewski
2004-09-03 8:28 ` Fabrice Bellard
2004-09-02 23:53 ` Daniel Serpell
2004-09-03 0:13 ` Jim C. Brown
2004-09-03 1:35 ` John R. Hogerhuis
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='002101c48ee5$46b2e280$20389c3f@computername' \
--to=jeebs@yango.us \
--cc=hetz@witch.dyndns.org \
--cc=qemu-devel@nongnu.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).