From: Riku Voipio <riku.voipio@iki.fi>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Blue Swirl <blauwirbel@gmail.com>,
juha.riihimaki@nokia.com, Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Unclear committer situation
Date: Wed, 2 Dec 2009 13:31:04 +0200 [thread overview]
Message-ID: <20091202113104.GA30508@kos.to> (raw)
In-Reply-To: <4B1565AD.10503@codemonkey.ws>
On Tue, Dec 01, 2009 at 12:51:25PM -0600, Anthony Liguori wrote:
>> There are some subsystems where nobody feels responsible though,
>> apparently hoping 'someone else' will tske on it. Well, turns out it
>> doesn't work that way.
> The general problem is that someone has to step up to maintain these
> subsystems. For some of them, there just isn't really a lot of interest.
I and Juha can take maintainence of the omap2 (and future omap3) stuff,
which obviously isn't mainted by anyone at the moment:
http://www.mail-archive.com/qemu-devel@nongnu.org/msg17487.html
http://lists.gnu.org/archive/html/qemu-devel/2009-06/msg00326.html
6 months for no action on a patch that fixes a "fails to boot" bug? No
wonder the android people have forked qemu so far...
> git pulls have been working really well for linux-user. I'd like to
> continue that for new architectures.
I can provide the patches in the same way as git pull requests.
next prev parent reply other threads:[~2009-12-02 11:31 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
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 [this message]
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=20091202113104.GA30508@kos.to \
--to=riku.voipio@iki.fi \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=juha.riihimaki@nokia.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.