From: Aurelien Jarno <aurelien@aurel32.net>
To: Leon Alrae <leon.alrae@imgtec.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"afaerber@suse.de" <afaerber@suse.de>,
aliguori@amazon.com,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] pending target-mips patches
Date: Thu, 16 Oct 2014 12:12:05 +0200 [thread overview]
Message-ID: <20141016101205.GP24004@hall.aurel32.net> (raw)
In-Reply-To: <542C1F52.6070901@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
Hi,
On Wed, Oct 01, 2014 at 04:35:46PM +0100, Leon Alrae wrote:
> Hi All,
>
> I noticed that it's quite difficult to get target-mips changes
> reviewed/accepted. There is already a queue of relatively big features
> and bug fixes which are stuck for months. Does anyone have an idea how
> to improve this situation? Wouldn't it help to have a target-mips
> co-maintainer assisting Aurelien?
I am sorry but I don't really have time to work on QEMU now, though I
hope to be able to contribute again in the next months. Adding a
co-maintainer for target-mips indeed looks the best to do. From what
I have seen, you, Leon Alrae, seems to be the good person for that.
Please send a patch updating the MAINTAINERS file with you name, I'll
ack it.
Cheers,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-10-16 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 15:35 [Qemu-devel] pending target-mips patches Leon Alrae
2014-10-01 16:32 ` Peter Maydell
2014-10-02 8:46 ` Leon Alrae
2014-10-01 16:33 ` Andreas Färber
2014-10-16 10:12 ` Aurelien Jarno [this message]
2014-10-16 10:19 ` Leon Alrae
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=20141016101205.GP24004@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=leon.alrae@imgtec.com \
--cc=peter.maydell@linaro.org \
--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).