qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Paul Brook <paul@codesourcery.com>,
	qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Use a Linux-style MAINTAINERS file
Date: Mon, 13 Sep 2010 20:41:00 +0200	[thread overview]
Message-ID: <4C8E703C.3030903@mail.berlios.de> (raw)
In-Reply-To: <1284067117-31127-1-git-send-email-aliguori@us.ibm.com>

Am 09.09.2010 23:18, schrieb Anthony Liguori:
> I make no claims that this is accurate or exhaustive but I think it's a
> reasonable place to start.
>
> As the file mentions, the purpose of this file is to give contributors
> information about who they can go to with questions about a particular piece of
> code or who they can ask for review.
>
> If you sign up for a piece of code and indicate that it's Maintained or
> Supported, please be prepared to be responsive to questions about that
> subsystem.
>
> Signed-off-by: Anthony Liguori<aliguori@us.ibm.com>
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 79dfc7f..3894cd8 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9,89 +9,388 @@ to be CC'd when submitting a patch to obtain appropriate review.
>   In general, if you have a question about inclusion of a patch, you should
>   consult qemu-devel and not any specific individual privately.
>
> -Project leaders:
> -----------------
> +Please see the MAINTAINERS file in the Linux kernel for information about how
> +to update this file.
>
> -Paul Brook
> -Anthony Liguori
> +General Project Administration
> +------------------------------
> +M: Anthony Liguori<aliguori@us.ibm.com>
> +M: Paul Brook<paul@codesourcery.com>
>   
[snip]

Hello Anthony,

you can add me for these parts:

block/vdi.c
hw/eepro100.c
hw/eeprom93xx.*

Regards,
Stefan

      parent reply	other threads:[~2010-09-13 18:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 21:18 [Qemu-devel] [PATCH] Use a Linux-style MAINTAINERS file Anthony Liguori
2010-09-09 21:35 ` [Qemu-devel] " Edgar E. Iglesias
2010-09-09 22:01   ` Anthony Liguori
2010-09-09 22:05 ` Alexander Graf
2010-09-10  8:03 ` Kevin Wolf
2010-09-10  8:10   ` Alexander Graf
2010-09-10  8:19     ` Kevin Wolf
2010-09-10  8:22       ` Alexander Graf
2010-09-10 11:30     ` Avi Kivity
2010-09-10 12:22       ` Alexander Graf
2010-09-10 12:26         ` Avi Kivity
2010-09-10 14:04   ` Anthony Liguori
2010-09-10 15:26     ` Venkateswararao Jujjuri (JV)
2010-09-10 15:46       ` Anthony Liguori
2010-09-10  8:25 ` Magnus Damm
2010-09-10 13:59   ` Anthony Liguori
2010-09-13 11:02     ` Magnus Damm
2010-09-10 13:29 ` Luiz Capitulino
2010-09-10 17:45 ` Blue Swirl
2010-09-10 19:05   ` Anthony Liguori
2010-09-10 19:19     ` Blue Swirl
2010-09-10 20:32       ` Andreas Färber
2010-09-10 22:17     ` Alexander Graf
2010-09-12  7:42 ` Blue Swirl
2010-09-12 13:12 ` Michael S. Tsirkin
2010-09-13 17:32 ` [Qemu-devel] " Anderson Lizardo
2010-09-13 18:29   ` Stefan Weil
2010-09-13 18:41 ` Stefan Weil [this message]

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=4C8E703C.3030903@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=aliguori@us.ibm.com \
    --cc=mst@redhat.com \
    --cc=paul@codesourcery.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).