From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Alexander Graf <agraf@suse.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Unclear committer situation
Date: Tue, 01 Dec 2009 15:08:08 -0600 [thread overview]
Message-ID: <4B1585B8.2030605@codemonkey.ws> (raw)
In-Reply-To: <f43fc5580912011121g34e41d0ckc240f8425c1f59bb@mail.gmail.com>
Blue Swirl wrote:
>>> Of course, my main unclear subsystems are PPC and S390.
>>>
>>> I'd recommend the following committers:
>>>
>>> PPC: Blue Swirl
>>> S390: Aurelien
>>>
>>> If you have other subsystems you feel uncertain on responsibilities,
>>> please add them to the list incl. committer recommendation.
>>>
>> PPC is tough because we lost our previous maintainer. It's generally in
>> pretty bad shape. No one really has stepped up to seriously improve it
>> either.
>>
>
> The design approach was often different from other architectures,
> which makes things like qdev conversion less trivial (see macio.c).
> Otherwise IMHO the situation has improved a lot, we even have a
> working BIOS. Only PREP has rotten.
>
Oh, no doubt. I didn't mean to minimize the work that's gone into it.
It's much better than it was a year ago.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-12-01 21:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 11:47 [Qemu-devel] Unclear committer situation Alexander Graf
2009-12-01 18:51 ` Anthony Liguori
2009-12-01 19:21 ` Blue Swirl
2009-12-01 21:08 ` Anthony Liguori [this message]
2009-12-01 22:49 ` Alexander Graf
2009-12-02 11:18 ` andrzej zaborowski
2009-12-02 11:24 ` Alexander Graf
2009-12-02 12:38 ` Avi Kivity
2009-12-02 11:31 ` Riku Voipio
2009-12-03 14:04 ` Anthony Liguori
2009-12-02 8:26 ` Aurelien Jarno
2009-12-02 8:37 ` Alexander Graf
2009-12-02 8:46 ` Aurelien Jarno
2009-12-02 8:54 ` Alexander Graf
2009-12-02 21:09 ` Jan-Simon Möller
2009-12-02 9:08 ` Avi Kivity
2009-12-02 8:45 ` malc
2009-12-02 15:33 ` Artyom Tarasenko
2009-12-02 18:31 ` [Qemu-devel] " Jan Kiszka
2009-12-02 18:48 ` Artyom Tarasenko
2009-12-03 10:20 ` Michael S. Tsirkin
2009-12-03 13:10 ` andrzej zaborowski
2009-12-02 21:18 ` Anthony Liguori
2009-12-03 10:07 ` Artyom Tarasenko
2009-12-02 18:40 ` [Qemu-devel] " Anthony Liguori
2009-12-02 18:53 ` Artyom Tarasenko
2009-12-02 18:56 ` Alexander Graf
2009-12-03 9:44 ` Filip Navara
2009-12-03 14:19 ` Anthony Liguori
2009-12-02 19:12 ` Anthony Liguori
2009-12-03 9:20 ` Riku Voipio
2009-12-03 12:56 ` Carl-Daniel Hailfinger
2009-12-03 14:40 ` [Qemu-devel] " Michael S. Tsirkin
2009-12-05 0:25 ` [Qemu-devel] " Isaku Yamahata
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=4B1585B8.2030605@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=blauwirbel@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.