From: Paolo Bonzini <pbonzini@redhat.com>
To: KVM list <kvm@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Christoffer Dall <christoffer.dall@linaro.org>,
Marc Zyngier <Marc.Zyngier@arm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
James Hogan <james.hogan@imgtec.com>,
Alexander Graf <agraf@suse.de>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Marcelo handling KVM tree for a few weeks
Date: Fri, 20 Feb 2015 18:02:26 +0100 [thread overview]
Message-ID: <54E768A2.60005@redhat.com> (raw)
KVM folks, Linus,
my second son should be getting out of his current cozy location very
soon, after which I'll be working part time for about a month.
During this period, I will not have enough time to devote to KVM
maintainership, and Marcelo will therefore take care of the kernel KVM
tree from next Monday until roughly the end of March. I will likely
handle the next merge window, but just to be safe, either I or Marcelo
will write again when things get back to normal on my side.
Thanks,
Paolo
reply other threads:[~2015-02-20 17:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54E768A2.60005@redhat.com \
--to=pbonzini@redhat.com \
--cc=Marc.Zyngier@arm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=christoffer.dall@linaro.org \
--cc=cornelia.huck@de.ibm.com \
--cc=james.hogan@imgtec.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=torvalds@linux-foundation.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