From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: berto@igalia.com, Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] MAINTAINERS leaves too many files uncovered
Date: Wed, 23 Sep 2015 10:24:55 +0200 [thread overview]
Message-ID: <20150923082455.GA4557@noname.redhat.com> (raw)
In-Reply-To: <560198FA.6040103@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
Am 22.09.2015 um 20:07 hat Eric Blake geschrieben:
> On 09/22/2015 03:13 AM, Markus Armbruster wrote:
>
> >> Full list of unmaintained files now:
> > [...]
> >
>
> > docs/bitmaps.md
> > docs/blkdebug.txt
> > docs/blkverify.txt
>
> > docs/live-block-ops.txt
>
> > docs/qcow2-cache.txt
> > docs/qdev-device-use.txt
>
> > docs/specs/qcow2.txt
> > docs/specs/qed_spec.txt
>
> Kevin, Stefan - should these be added to Block maintainers?
Except for docs/qdev-device-use.txt, I guess.
Also, they shouldn't be added to block in general, but to the specific
block drivers/subsystems like qcow2, qed, block jobs etc.
> > include/qemu/throttle.h
>
> Block?
Would be covered if it were in the correct place (include/block/).
Should we add a separate section for I/O throttling, maintained by
Berto, as well? So far it's part of the block layer core - that is,
officially maintained by me and I know next to nothing about it.
Kevin
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-09-23 8:25 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 9:19 [Qemu-devel] MAINTAINERS leaves too many files uncovered Markus Armbruster
2014-10-20 18:36 ` Paolo Bonzini
2014-10-22 8:23 ` Markus Armbruster
2014-10-22 9:00 ` Paolo Bonzini
2014-10-22 11:45 ` Markus Armbruster
2014-10-22 11:50 ` Paolo Bonzini
2014-10-22 13:06 ` Markus Armbruster
2014-10-22 13:22 ` Alexander Graf
2014-10-22 13:36 ` Paolo Bonzini
2014-10-22 11:58 ` [Qemu-devel] MAINTAINERS: please add myself as usb-serial.c and baum.c maintainer Samuel Thibault
2014-10-22 12:51 ` Paolo Bonzini
2014-10-22 13:00 ` Markus Armbruster
2014-10-22 13:53 ` Samuel Thibault
2014-10-22 15:21 ` Markus Armbruster
2014-10-22 12:06 ` [Qemu-devel] MAINTAINERS leaves too many files uncovered Michael Roth
2014-10-22 12:54 ` Luiz Capitulino
2015-09-22 9:13 ` Markus Armbruster
2015-09-22 10:06 ` Daniel P. Berrange
2015-09-22 10:18 ` Paolo Bonzini
2015-09-22 13:42 ` Thomas Huth
2015-09-22 14:58 ` Gerd Hoffmann
2015-09-22 15:13 ` Juan Quintela
2015-09-22 14:58 ` Daniel P. Berrange
2015-09-22 15:40 ` Peter Maydell
2015-09-22 18:07 ` Eric Blake
2015-09-22 19:50 ` Paolo Bonzini
2015-09-23 8:24 ` Kevin Wolf [this message]
2015-09-23 8:30 ` Alberto Garcia
2015-09-24 12:49 ` Markus Armbruster
2015-09-24 12:47 ` Markus Armbruster
2015-09-22 18:37 ` John Snow
2016-08-30 11:31 ` Markus Armbruster
2016-08-30 12:26 ` Cornelia Huck
2016-08-30 12:40 ` Paolo Bonzini
2016-08-30 13:29 ` Cornelia Huck
2016-08-30 12:48 ` Paolo Bonzini
2016-08-30 12:57 ` Peter Maydell
2016-08-30 18:31 ` John Snow
2016-08-30 14:47 ` Paolo Bonzini
2016-08-30 15:29 ` Markus Armbruster
2016-08-30 15:33 ` Paolo Bonzini
2016-08-31 8:28 ` Markus Armbruster
2016-08-30 13:39 ` Cornelia Huck
2016-09-12 13:56 ` Thomas Huth
2016-09-23 12:56 ` Thomas Huth
2016-09-23 14:47 ` Thomas Huth
2018-11-21 18:14 ` Markus Armbruster
2018-11-22 12:22 ` Thomas Huth
2018-11-22 21:56 ` BALATON Zoltan
2018-11-23 5:17 ` Philippe Mathieu-Daudé
2018-11-23 10:56 ` BALATON Zoltan
2018-11-23 11:03 ` Philippe Mathieu-Daudé
2018-11-26 13:54 ` Markus Armbruster
2014-10-22 14:02 ` Alex Bennée
2014-10-22 15:26 ` Markus Armbruster
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=20150923082455.GA4557@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=eblake@redhat.com \
--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 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).