From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1DYFur-0001db-IP
	for qemu-devel@nongnu.org; Wed, 18 May 2005 00:12:19 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1DYFui-0001bh-MG
	for qemu-devel@nongnu.org; Wed, 18 May 2005 00:12:09 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1DYFuh-0001WQ-Rm
	for qemu-devel@nongnu.org; Wed, 18 May 2005 00:12:08 -0400
Received: from [64.233.184.192] (helo=wproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1DYFyg-000715-IF
	for qemu-devel@nongnu.org; Wed, 18 May 2005 00:16:14 -0400
Received: by wproxy.gmail.com with SMTP id 71so100547wra
	for <qemu-devel@nongnu.org>; Tue, 17 May 2005 21:07:57 -0700 (PDT)
Message-ID: <dd8f98f405051721077d31756a@mail.gmail.com>
Date: Tue, 17 May 2005 21:07:57 -0700
From: John Hogerhuis <jhoger@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] slirp 64-bit fixes
In-Reply-To: <Pine.LNX.4.58.0505171054360.21768@thalys.mandrakesoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <Pine.LNX.4.58.0505171054360.21768@thalys.mandrakesoft.com>
Reply-To: jhoger@pobox.com, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Curious if the patches to slirp are being forwarded upstream to the
current slirp maintainer.

I wonder if he even knows QEMU uses it?

http://lists.sourceforge.net/lists/listinfo/slirp-devel

-- John.