From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-block@nongnu.org, qemu-trivial@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, "Max Reitz" <mreitz@redhat.com>,
"John Snow" <jsnow@redhat.com>
Subject: Re: [PATCH 2/3] MAINTAINERS: Cover qapi/block{-core}.json in 'Block layer core' section
Date: Fri, 7 Feb 2020 15:21:46 +0100 [thread overview]
Message-ID: <20200207142146.GF6031@linux.fritz.box> (raw)
In-Reply-To: <87blqaqyxi.fsf@dusky.pond.sub.org>
Am 07.02.2020 um 15:01 hat Markus Armbruster geschrieben:
> Philippe Mathieu-Daudé <philmd@redhat.com> writes:
>
> > List this file in the proper section, so maintainers get
> > notified when it is modified.
> >
> > Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> > ---
> > Cc: Kevin Wolf <kwolf@redhat.com>
> > Cc: Max Reitz <mreitz@redhat.com>
> > Cc: qemu-block@nongnu.org
> > ---
> > MAINTAINERS | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 903831e0a4..e269e9092c 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -1842,6 +1842,8 @@ S: Supported
> Block layer core
> M: Kevin Wolf <kwolf@redhat.com>
> M: Max Reitz <mreitz@redhat.com>
> L: qemu-block@nongnu.org
> S: Supported
> > F: block*
> > F: block/
> > F: hw/block/
> > +F: qapi/block.json
> > +F: qapi/block-core.json
> > F: include/block/
> > F: qemu-img*
> > F: docs/interop/qemu-img.rst
>
> This is in addition to
>
> Block QAPI, monitor, command line
> M: Markus Armbruster <armbru@redhat.com>
> S: Supported
> F: blockdev.c
> F: block/qapi.c
> F: qapi/block*.json
> F: qapi/transaction.json
> T: git https://repo.or.cz/qemu/armbru.git block-next
>
> I'm not sure this section makes much sense anymore.
This is probably for you to decide.
Though the block-next branch from the T: line doesn't even exist any
more...
> Should qapi/transaction.json also be added to "Block layer core"? Or
> should it go into John's section "Block Jobs"?
I think at the moment it only supports actions that are more related to
block jobs, so moving it there would make sense to me.
Kevin
next prev parent reply other threads:[~2020-02-07 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 10:30 [PATCH 0/3] MAINTAINERS: Cover orphean qapi/json files Philippe Mathieu-Daudé
2020-02-07 10:30 ` [PATCH 1/3] MAINTAINERS: Cover qapi/rocker.json in 'Rocker' section Philippe Mathieu-Daudé
2020-02-07 10:30 ` [PATCH 2/3] MAINTAINERS: Cover qapi/block{-core}.json in 'Block layer core' section Philippe Mathieu-Daudé
2020-02-07 10:56 ` Max Reitz
2020-02-07 14:01 ` Markus Armbruster
2020-02-07 14:21 ` Kevin Wolf [this message]
2020-02-07 16:07 ` Markus Armbruster
2020-02-07 16:27 ` Philippe Mathieu-Daudé
2020-02-07 10:30 ` [PATCH 3/3] MAINTAINERS: Cover qapi/trace.json in 'Tracing' section Philippe Mathieu-Daudé
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=20200207142146.GF6031@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).