From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GQ77D-0003tV-Q6 for qemu-devel@nongnu.org; Wed, 20 Sep 2006 14:48:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GQ77D-0003sk-2p for qemu-devel@nongnu.org; Wed, 20 Sep 2006 14:48:11 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GQ77C-0003sa-TX for qemu-devel@nongnu.org; Wed, 20 Sep 2006 14:48:10 -0400 Received: from [64.233.162.198] (helo=nz-out-0102.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GQ7AY-0000fH-8G for qemu-devel@nongnu.org; Wed, 20 Sep 2006 14:51:38 -0400 Received: by nz-out-0102.google.com with SMTP id n29so188079nzf for ; Wed, 20 Sep 2006 11:48:10 -0700 (PDT) Message-ID: <7fac565a0609201148q5782a2a1w7ec52d3febfaf277@mail.gmail.com> Date: Wed, 20 Sep 2006 20:48:09 +0200 From: "Alexey Eremenko" Subject: Re: Re[2]: [Qemu-devel] Poor Qemu documentation for Windows host In-Reply-To: <489863085.20060919025017@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_240488_686130.1158778089532" References: <7fac565a0609172005w355fd473p4ecc3183390bc212@mail.gmail.com> <1158549358.4008.1.camel@vaio> <7fac565a0609181217m47ce48bbw94eb4944b67e6c19@mail.gmail.com> <489863085.20060919025017@gmail.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ------=_Part_240488_686130.1158778089532 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline > > > Next step, I can build an integrated Qemu setup package for Windows, > > that has TAP-Win32 drivers in it. (that way I will follow the standard > > rule of Windows to depend *just* on the OS itself) > > But I will only do this setup, if you agree to list it on Qemu homesite. > > And again, it comes not to doing something, but to maintaining and > supporting that. Because otherwise, in a year, only broken links will remind > of good intentions, or in the best case, outdated binaries of unknown > origin. > > > So, however it may seem overcomplicated, more sustained way to get > better Windows support is indeed to submit doc patches, cooperate with Win32 > maintainer on improving his site/packaging, or start your own > Win32 port project and see if you can do better. > > > Anyway, I really hope that I'm wrong and your packaging contribution > will be accepted without much hassle, to rejoice of all us, Windows users. OK, agreed. Where may I find the so-called "Win32 maintainer" to ask about integrating TAP-Win32 drivers and some additions into the package. Does he listens to this list? ------=_Part_240488_686130.1158778089532 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline
> Next step, I can build an integrated Qemu setup package for Windows,
> that has TAP-Win32 drivers in it. (that way I will follow the standard
> rule of Windows to depend *just* on the OS itself)
> But I will only do this setup, if you agree to list it on Qemu homesite.

  And again, it comes not to doing something, but to maintaining and supporting that. Because otherwise, in a year, only broken links will remind of good intentions, or in the best case, outdated binaries of unknown origin.


  So, however it may seem overcomplicated, more sustained way to get better Windows support is indeed to submit doc patches, cooperate with Win32 maintainer on improving his site/packaging, or start your own
Win32 port project and see if you can do better.


  Anyway, I really hope that I'm wrong and your packaging contribution will be accepted without much hassle, to rejoice of all us, Windows users.

 
OK, agreed. Where may I find the so-called "Win32 maintainer" to ask about integrating TAP-Win32 drivers and some additions into the package. Does he listens to this list?

------=_Part_240488_686130.1158778089532--