From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org, Alex Pyrgiotis <apyrgio@arrikto.com>,
Daniel Berrange <berrange@redhat.com>,
Janosch Frank <frankja@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] could someone else handle the "misc" patches for a few months?
Date: Mon, 11 Jan 2016 22:04:11 +0100 [thread overview]
Message-ID: <569418CB.2030707@redhat.com> (raw)
In-Reply-To: <n2585i$rp5$1@ger.gmane.org>
On 13/11/2015 18:54, Paolo Bonzini wrote:
> Hi,
>
> I would like someone else to handle miscellaneous patches for the rest
> of the 2.5 release as well as for 2.6.
>
> The main thing to cover here is the build stuff, especially configure,
> and the documentation. I would still handle
> cpu-exec.c/exec.c/translate-all.c and friends, for which I've sent a
> MAINTAINERS patch right now.
There was no volunteer so, as expected, there might be delays in my
processing of other people's patches. Sorry. I hope things get a bit
better about a month from now.
Paolo
prev parent reply other threads:[~2016-01-11 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 17:54 [Qemu-devel] could someone else handle the "misc" patches for a few months? Paolo Bonzini
2016-01-11 21:04 ` Paolo Bonzini [this message]
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=569418CB.2030707@redhat.com \
--to=pbonzini@redhat.com \
--cc=apyrgio@arrikto.com \
--cc=berrange@redhat.com \
--cc=frankja@linux.vnet.ibm.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.