From: Paolo Bonzini <pbonzini@redhat.com>
To: mhines@digitalocean.com, qemu-devel@nongnu.org
Cc: lizhijian@cn.fujitsu.com, zhang.zhanghailiang@huawei.com,
quintela@redhat.com, skottler@digitalocean.com,
"Michael R. Hines" <michael@hinespot.com>,
dgilbert@redhat.com, arei.gonglei@huawei.com, chegu_vinod@hp.com
Subject: Re: [Qemu-devel] [PATCH: 2/2] maintainers: changed companies, use an email that doesn't change
Date: Wed, 16 Sep 2015 11:46:53 +0200 [thread overview]
Message-ID: <55F93A8D.4060509@redhat.com> (raw)
In-Reply-To: <1442339207-19646-2-git-send-email-mhines@digitalocean.com>
On 15/09/2015 19:46, mhines@digitalocean.com wrote:
> From: "Michael R. Hines" <michael@hinespot.com>
>
> Is there a procedure for updating this file besides just updating the
> file?
Not really, more maintainers are always welcome. :)
Paolo
> Signed-off-by: Michael R. Hines <michael@hinespot.com>
> ---
> MAINTAINERS | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 688979b..c455533 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1066,6 +1066,12 @@ F: migration/
> F: scripts/vmstate-static-checker.py
> F: tests/vmstate-static-checker-data/
>
> +RDMA Migration
> +M: Michael R. Hines <michael@hinespot.com>
> +M: Michael R. Hines <mhines@digitalocean.com>
> +S: Maintained
> +F: migration/rdma.c
> +
> Seccomp
> M: Eduardo Otubo <eduardo.otubo@profitbricks.com>
> S: Supported
>
next prev parent reply other threads:[~2015-09-16 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 17:46 [Qemu-devel] [PATCH: 1/2] rdma: changed companies, use an email that doesn't change mhines
2015-09-15 17:46 ` [Qemu-devel] [PATCH: 2/2] maintainers: " mhines
2015-09-16 9:46 ` Paolo Bonzini [this message]
2015-09-16 9:46 ` [Qemu-devel] [PATCH: 1/2] rdma: " Paolo Bonzini
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=55F93A8D.4060509@redhat.com \
--to=pbonzini@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=chegu_vinod@hp.com \
--cc=dgilbert@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=mhines@digitalocean.com \
--cc=michael@hinespot.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=skottler@digitalocean.com \
--cc=zhang.zhanghailiang@huawei.com \
/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).