From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel][PATCH] Tap and VLAN socket support for win32
Date: Tue, 07 Feb 2006 22:44:16 +0100 [thread overview]
Message-ID: <43E914B0.6060808@bellard.org> (raw)
In-Reply-To: <20060207211810.GA31289@jbrown.mylinuxbox.org>
Jim C. Brown wrote:
> On Thu, Feb 02, 2006 at 12:10:36AM +0100, Fabrice Bellard wrote:
>
>>Hi,
>>
>>I merged your patches and I made important changes to simplify them. I
>>did not do any tests so tell me if you see problems.
>>
>>Regards,
>>
>>Fabrice.
>>
>
>
> Have you decided to accept the GPL license on it then?
>
> http://lists.gnu.org/archive/html/qemu-devel/2004-10/msg00217.html
Yes because the features are packed in a single file which can be
removed if needed.
Fabrice.
next prev parent reply other threads:[~2006-02-07 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 7:34 [Qemu-devel][PATCH] Tap and VLAN socket support for win32 Kazu
2006-01-31 16:00 ` André Braga
2006-02-01 23:10 ` Fabrice Bellard
2006-02-02 10:03 ` Kazu
2006-02-04 18:28 ` Fabrice Bellard
2006-02-09 2:29 ` Kazu
2006-02-09 14:00 ` Kazu
2006-02-05 4:05 ` Jim C. Brown
2006-02-07 21:18 ` Jim C. Brown
2006-02-07 21:44 ` Fabrice Bellard [this message]
2006-02-08 7:23 ` David Fraser
2006-02-08 7:32 ` M. Warner Losh
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=43E914B0.6060808@bellard.org \
--to=fabrice@bellard.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).