From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: user-net -redir working? [problem located][PATCH]
Date: Wed, 23 Nov 2005 10:55:41 -0500 [thread overview]
Message-ID: <20051123155540.GA16888@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <E1Eeq7O-0007xT-5Y@smtp2.mail.be.easynet.net>
On Wed, Nov 23, 2005 at 08:33:06AM +0000, Mark Jonckheere wrote:
> Richard Neill schreef:
>
> 4)lookup the mailing list archive and find out that this problem
> has already been detected, diagnosed, resolved and completely ignored
> more than a year ago.
>
And sadly, it seems it is being ignored once again. (I didn't actually get that
email back in Sept 2004. It is possible that it might have missed Fabrice as
well.)
Fabrice really should commit this to CVS.
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
prev parent reply other threads:[~2005-11-23 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 22:04 [Qemu-devel] Re: user-net -redir working? [problem located] Richard Neill
2005-11-23 8:33 ` [Qemu-devel] Re: user-net -redir working? [problem located][PATCH] Mark Jonckheere
2005-11-23 15:55 ` Jim C. Brown [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=20051123155540.GA16888@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--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).