From: Fabrice Bellard <fabrice@bellard.org>
To: jhoger@pobox.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU News: Win32 Port
Date: Thu, 01 Apr 2004 02:06:30 +0200 [thread overview]
Message-ID: <406B5D06.6030006@bellard.org> (raw)
In-Reply-To: <1080777092.3138.10.camel@aragorn>
John R. Hogerhuis wrote:
> So at one point and who should post a story to Slashdot or another news
> site about Kazu's port? I'd personally call this newsworthy. And it
> could bring a spike of new interest to the project that could help get
> the remaining drivers knocked out, and probably even more interest for
> QEMU generally.
Before making an "official" announce, it is better to wait for the 0.5.3
release as it contains big improvements compared to the 0.5.2 (I will
release it before the end of the week).
Fabrice.
next prev parent reply other threads:[~2004-04-01 0:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 23:36 [Qemu-devel] QEMU News: Win32 Port Fabrice Bellard
2004-03-31 23:45 ` [Qemu-devel] " Fabrice Bellard
2004-04-01 2:25 ` Lennert Buytenhek
2004-04-01 4:07 ` John R. Hogerhuis
2004-04-01 8:07 ` Lennert Buytenhek
2004-04-01 7:09 ` John R. Hogerhuis
2004-04-01 8:39 ` John R. Hogerhuis
2004-03-31 23:51 ` [Qemu-devel] " John R. Hogerhuis
2004-04-01 0:06 ` Fabrice Bellard [this message]
2004-04-01 7:43 ` [Qemu-devel] QEMU News: Win32 Port - Release Schedule Rudi Lippert
2004-04-01 8:06 ` Hetz Ben Hamo
2004-04-01 8:25 ` Rudi Lippert
2004-04-01 9:24 ` John R. Hogerhuis
2004-04-01 9:30 ` Gaël Varoquaux
2004-04-01 9:58 ` Rudi Lippert
2004-04-01 22:01 ` Fabrice Bellard
2004-04-01 8:55 ` Jean-Michel POURE
2004-04-01 12:26 ` Lionel Ulmer
2004-04-01 13:42 ` Rudi Lippert
2004-04-02 23:26 ` Mark IJbema
2004-04-03 9:35 ` Wesley Parish
2004-04-01 16:31 ` [Qemu-devel] FreeBSD port (was: QEMU News: Win32 Port) Markus Niemistö
2004-04-03 17:11 ` [Qemu-devel] QEMU News: Win32 Port kazu
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=406B5D06.6030006@bellard.org \
--to=fabrice@bellard.org \
--cc=jhoger@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.