From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Modular qemu?
Date: Fri, 05 Dec 2008 09:25:05 -0600 [thread overview]
Message-ID: <493947D1.9010609@codemonkey.ws> (raw)
In-Reply-To: <761ea48b0812050652p1608020fw93051708e7e95d14@mail.gmail.com>
Laurent Desnogues wrote:
> 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.
>
Yeah, I understand that the linux-user stuff is currently unmaintained.
Just appointing someone is really the right approach either. With the
kernel.org git mirror, it would be relatively easy for someone to
maintain a linux-user tree.
If someone were to do that, they could post pull requests. I think it's
then natural to promote the maintainer of such a tree to an official
maintainer.
It just requires someone willing to put in the time. git is not the
only option, just maintaining a patch queue for linux-user would be a
good start too.
Regards,
Anthony Liguori
> Laurent
>
>
>
next prev parent reply other threads:[~2008-12-05 15:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 10:53 [Qemu-devel] Modular qemu? Joop Boonen
2008-12-05 12:40 ` Carl-Daniel Hailfinger
2008-12-05 14:32 ` Anthony Liguori
2008-12-05 14:52 ` Laurent Desnogues
2008-12-05 15:07 ` Glauber Costa
2008-12-05 15:29 ` Anthony Liguori
2008-12-05 15:25 ` Anthony Liguori [this message]
2008-12-05 18:19 ` Avi Kivity
2008-12-05 18:54 ` Thiemo Seufer
2008-12-05 19:02 ` Avi Kivity
2008-12-05 19:27 ` Anthony Liguori
2008-12-05 19:37 ` Avi Kivity
2008-12-05 19:58 ` Anthony Liguori
2008-12-05 18:56 ` [Qemu-devel] " Jan Kiszka
2008-12-05 18:57 ` [Qemu-devel] " Anthony Liguori
2008-12-05 19:12 ` Avi Kivity
2008-12-09 13:06 ` Jun Koi
2008-12-09 13:17 ` Stefano Stabellini
2008-12-09 13:44 ` Avi Kivity
2008-12-05 22:10 ` Edgar E. Iglesias
2008-12-06 13:23 ` Lionel Landwerlin
2008-12-08 10:15 ` Stefano Stabellini
2008-12-17 13:34 ` Ian Jackson
-- strict thread matches above, loose matches on Subject: below --
2008-12-08 23:58 Salvatore Lionetti
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=493947D1.9010609@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).