qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>
Subject: [Qemu-devel] [PATCH] migration: add a MAINTAINERS entry for migration
Date: Sat, 12 Nov 2011 10:07:54 -0600	[thread overview]
Message-ID: <1321114074-3681-1-git-send-email-aliguori@us.ibm.com> (raw)

I think this is an accurate reflection of the state of migration today.  This
is the second release in a row where we're scrambling to fix a critical issue
in migration.

The first step in fixing this problem is being up front about what the current
state of the subsystem is.  If we're going to treat migration as a release
blocking feature in the future, than we need to promote the migration subsystem
above 'Odd Fixes' status.

Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
---
 MAINTAINERS |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 7ee301e..45b345f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -461,6 +461,11 @@ M: Anthony Liguori <aliguori@us.ibm.com>
 S: Supported
 F: vl.c
 
+Migration
+M: Anthony Liguori <aliguori@us.ibm.com>
+S: Odd Fixes
+F: migration*.c savevm.c
+
 Monitor (QMP/HMP)
 M: Luiz Capitulino <lcapitulino@redhat.com>
 M: Markus Armbruster <armbru@redhat.com>
-- 
1.7.4.1

             reply	other threads:[~2011-11-12 16:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-12 16:07 Anthony Liguori [this message]
2011-11-14 17:40 ` [Qemu-devel] [PATCH] migration: add a MAINTAINERS entry for migration Juan Quintela
2011-11-14 21:08   ` Anthony Liguori
2011-11-15  8:32     ` Stefan Hajnoczi
2011-11-15 13:04       ` Avi Kivity
2011-11-15 13:45       ` Anthony Liguori
2011-11-15  9:36     ` Kevin Wolf
2011-11-15 13:50       ` Anthony Liguori

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=1321114074-3681-1-git-send-email-aliguori@us.ibm.com \
    --to=aliguori@us.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 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).