From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, libvir-list@redhat.com,
pkrempa@redhat.com, berrange@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] MAINTAINERS: New section "Incompatible changes", copy libvir-list
Date: Mon, 16 Jul 2018 10:02:13 +0200 [thread overview]
Message-ID: <20180716100213.25c44c16.cohuck@redhat.com> (raw)
In-Reply-To: <c2d21b05-0065-80ae-6863-c06f27b448bf@redhat.com>
On Mon, 16 Jul 2018 09:54:12 +0200
Thomas Huth <thuth@redhat.com> wrote:
> On 16.07.2018 09:32, Markus Armbruster wrote:
> > Libvirt developers would like to be copied on patches to qemu-doc
> > appendix "Deprecated features". Do them the favor.
> >
> > Signed-off-by: Markus Armbruster <armbru@redhat.com>
> > ---
> > MAINTAINERS | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 20eef3cb61..666e936812 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -2194,6 +2194,10 @@ M: Daniel P. Berrange <berrange@redhat.com>
> > S: Odd Fixes
> > F: docs/devel/build-system.txt
> >
> > +Incompatible changes
> > +R: libvir-list@redhat.com
> > +F: qemu-deprecated.texi
>
> Should we have a maintainer for the file, too? (I guess not, because
> deprecation patches should go through the specific subsystems...)
I don't think adding a maintainer makes sense for this file.
> And what about a "S:" line?
I don't think that makes too much sense, either.
If anything, qemu-deprecated.texi should be in a category 'maintained
by everybody', i.e. qemu-devel. Just like qemu-doc.texi, which does not
have an entry in MAINTAINERS at all.
next prev parent reply other threads:[~2018-07-16 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 7:32 [Qemu-devel] [PATCH 0/2] Make it easier to track feature deprecation Markus Armbruster
2018-07-16 7:32 ` [Qemu-devel] [PATCH 1/2] qemu-doc: Move appendix "Deprecated features" to its own file Markus Armbruster
2018-07-16 7:50 ` Thomas Huth
2018-07-16 7:54 ` Cornelia Huck
2018-07-16 9:41 ` Daniel P. Berrangé
2018-07-16 7:32 ` [Qemu-devel] [PATCH 2/2] MAINTAINERS: New section "Incompatible changes", copy libvir-list Markus Armbruster
2018-07-16 7:54 ` Thomas Huth
2018-07-16 8:02 ` Cornelia Huck [this message]
2018-07-16 13:46 ` Markus Armbruster
2018-07-16 7:55 ` Cornelia Huck
2018-07-16 9:39 ` Daniel P. Berrangé
2018-07-24 15:59 ` [Qemu-devel] [libvirt] " Eric Blake
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=20180716100213.25c44c16.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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.