From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
netdev@vger.kernel.org
Subject: VIRTIO/VHOST maintainer availability for 3.16/3.17
Date: Sun, 6 Jul 2014 10:44:14 +0300 [thread overview]
Message-ID: <20140706074414.GA17130@redhat.com> (raw)
Hi guys,
This is just to let you know that I'll be traveling starting Tuesday,
July 8 and until July 27. I won't be able to attend the KVM developers
conference call or other meetings, but I plan to check mail every 1-2
days so this should be transparent to you, and there should be no
problem in case there are high priority bugfixes.
However, please do the following to make it less likely for me to miss
an important patch from you:
- cc me on the patches that need my attention
- tag patches appropriately with for-3.16/for-3.17 in the subject
- tag patches that aren't for 3.16/3.17 as RFC in the subject,
and plan to repost as non RFC later
I plan to be online as usual from July 28, should be just in time for
3.16 release and 3.17 merge window.
Ciao,
--
MST
reply other threads:[~2014-07-06 7:44 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=20140706074414.GA17130@redhat.com \
--to=mst@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.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;
as well as URLs for NNTP newsgroup(s).