From: Derek Fawcus <dfawcus@cisco.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Qemu floppy emulation problems - partially solved
Date: Mon, 4 Oct 2004 23:00:30 +0100 [thread overview]
Message-ID: <20041004230030.B20135@edinburgh.cisco.com> (raw)
In-Reply-To: <416073E6.6080009@bellard.org>; from fabrice@bellard.org on Sun, Oct 03, 2004 at 11:49:26PM +0200
On Sun, Oct 03, 2004 at 11:49:26PM +0200, Fabrice Bellard wrote:
> Applied a modified version. Tell me if it works.
Well I was waiting to here back if the change I proposed had any
positive effects, since I'm not experiencing the problems it's
supposed to address.
However I've had no feedback, so it's a bit difficult to tell
if it's of help.
DF
next prev parent reply other threads:[~2004-10-04 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 15:35 [Qemu-devel] Re: Qemu floppy emulation problems - partially solved Mike Nordell
2004-08-31 16:55 ` Derek Fawcus
2004-10-03 21:49 ` Fabrice Bellard
2004-10-04 22:00 ` Derek Fawcus [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-07 13:37 Mike Nordell
2004-10-07 17:13 ` Derek Fawcus
2004-10-08 9:39 Mike Nordell
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=20041004230030.B20135@edinburgh.cisco.com \
--to=dfawcus@cisco.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 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).