From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Andreas Färber" <andreas.faerber@web.de>,
qemu-devel@nongnu.org, "Anthony Liguori" <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: add self as virtio co-maintainer
Date: Mon, 27 Jan 2014 15:26:57 +0200 [thread overview]
Message-ID: <20140127132657.GA11895@redhat.com> (raw)
In-Reply-To: <20140127105105.GB11887@stefanha-thinkpad.redhat.com>
On Mon, Jan 27, 2014 at 11:51:05AM +0100, Stefan Hajnoczi wrote:
> On Mon, Jan 27, 2014 at 10:37:16AM +0100, Kevin Wolf wrote:
> > Am 26.01.2014 um 11:40 hat Michael S. Tsirkin geschrieben:
> > > This will help make sure I get Cc'd on patches.
> >
> > You wish...
> >
> > This won't change the actual responsibility, i.e. patches to virtio-blk
> > are still meant to be merged through the block tree, right? It's just so
> > you get a chance to comment?
>
> The proper way to document that is for us to split out virtio-blk.c and
> add the block tree git repo URL. Let's avoid informal agreements so
> that maintainership is clear to everyone from just the ./MAINTAINERS file.
>
> Stefan
MAINTAINERS is really about getting all the right people Cc'd.
Who merges what can't be formalized using regular expressions:
it depends on more than which files are changed.
--
MST
next prev parent reply other threads:[~2014-01-27 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 10:40 [Qemu-devel] [PATCH] MAINTAINERS: add self as virtio co-maintainer Michael S. Tsirkin
2014-01-27 9:37 ` Kevin Wolf
2014-01-27 10:51 ` Stefan Hajnoczi
2014-01-27 13:26 ` Michael S. Tsirkin [this message]
2014-01-27 10:53 ` Michael S. Tsirkin
2014-01-27 15:47 ` Kevin Wolf
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=20140127132657.GA11895@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@amazon.com \
--cc=andreas.faerber@web.de \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.