From: Josh Metzler <joshdeb@metzlers.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Anyone familiar with the slirp code?
Date: Fri, 22 Jul 2005 18:29:46 -0400 [thread overview]
Message-ID: <200507221829.46143.joshdeb@metzlers.org> (raw)
In-Reply-To: <20050722155125.GC3558@cel.leo>
On Friday 22 July 2005 11:51 am, Paul LeoNerd Evans wrote:
> Hi all again,
>
> I'm looking over the slirp code, trying to work out the exact nature of
> this AMD64 bug.
...
> Is anyone here familiar with the way the code is intended to run..? I
> would like to get to the bottom of the issue, and fix it in a proper
> robust way...
You might want to ask the colinux developers, too, as I believe they have
been doing some work on slirp for their project.
Josh
prev parent reply other threads:[~2005-07-22 22:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 15:51 [Qemu-devel] Anyone familiar with the slirp code? Paul LeoNerd Evans
2005-07-22 16:47 ` John R. Hogerhuis
2005-07-22 18:14 ` Paul LeoNerd Evans
2005-07-22 18:45 ` Gwenole Beauchesne
2005-07-22 22:05 ` Jim C. Brown
2005-07-22 22:53 ` Gwenole Beauchesne
2005-07-23 4:15 ` Jim C. Brown
2005-07-24 18:09 ` Adrian Smarzewski
2005-07-22 22:29 ` Josh Metzler [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=200507221829.46143.joshdeb@metzlers.org \
--to=joshdeb@metzlers.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).