From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1L8c2x-0006Pp-3a
	for qemu-devel@nongnu.org; Fri, 05 Dec 2008 09:52:47 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1L8c2w-0006PV-F6
	for qemu-devel@nongnu.org; Fri, 05 Dec 2008 09:52:46 -0500
Received: from [199.232.76.173] (port=42036 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1L8c2w-0006PO-6a
	for qemu-devel@nongnu.org; Fri, 05 Dec 2008 09:52:46 -0500
Received: from ey-out-1920.google.com ([74.125.78.147]:60386)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <laurent.desnogues@gmail.com>) id 1L8c2v-00075Q-MJ
	for qemu-devel@nongnu.org; Fri, 05 Dec 2008 09:52:45 -0500
Received: by ey-out-1920.google.com with SMTP id 4so14843eyk.4
	for <qemu-devel@nongnu.org>; Fri, 05 Dec 2008 06:52:44 -0800 (PST)
Message-ID: <761ea48b0812050652p1608020fw93051708e7e95d14@mail.gmail.com>
Date: Fri, 5 Dec 2008 15:52:44 +0100
From: "Laurent Desnogues" <laurent.desnogues@gmail.com>
Subject: Re: [Qemu-devel] Modular qemu?
In-Reply-To: <49393B8D.40209@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3056442136ca43729c6a2aec02c038aa.squirrel@www.boonen.name>
	<49393B8D.40209@codemonkey.ws>
Reply-To: 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

On Fri, Dec 5, 2008 at 3:32 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
> With respect to the various forks of QEMU, I believe the real problem is
> that historically, people have had a tough time getting changes into QEMU.
>  This is not just a matter of getting patches accepted, but also getting the
> appropriate guidance about how to refactor things to take into account all
> of the various architecture combinations that QEMU supports and some of the
> longer term efforts.
>
> I hope this situation is improving.  If people have feedback in how things
> could be improved, I think everyone is eager to here it.  Plugins are not
> the solution though.

Sorry to say, but many forks are linux-user ones and qemu has no
maintainer for that.  This might become even worse in the future
with, for instance, Nokia using qemu linux-user for the SDK of their
upcoming OMAP3 based tablet.


Laurent