From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
rth@twiddle.net, "Andreas Färber" <afaerber@suse.de>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PATCH 0/2] MAINTAINERS: X86 update
Date: Wed, 8 Apr 2015 13:57:34 -0300 [thread overview]
Message-ID: <1428512256-17707-1-git-send-email-ehabkost@redhat.com> (raw)
Add myself as X86 maintainer, and change its status to "Maintained".
Eduardo Habkost (2):
MAINTAINERS: Add myself to X86
MAINTAINERS: Change status of X86 to Maintained
MAINTAINERS | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
2.1.0
next reply other threads:[~2015-04-08 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 16:57 Eduardo Habkost [this message]
2015-04-08 16:57 ` [Qemu-devel] [PATCH 1/2] MAINTAINERS: Add myself to X86 Eduardo Habkost
2015-04-08 16:57 ` [Qemu-devel] [PATCH 2/2] MAINTAINERS: Change status of X86 to Maintained Eduardo Habkost
2015-04-09 8:52 ` [Qemu-devel] [PATCH 0/2] MAINTAINERS: X86 update 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=1428512256-17707-1-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=afaerber@suse.de \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).