From: Cornelia Huck <cohuck@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org,
"Aleksandar Markovic" <aleksandar.m.mail@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] MAINTAINERS: Improve section headlines
Date: Mon, 3 Jun 2019 11:35:18 +0200 [thread overview]
Message-ID: <20190603113518.4cce7e76.cohuck@redhat.com> (raw)
In-Reply-To: <87k1e3t6kw.fsf@dusky.pond.sub.org>
On Mon, 03 Jun 2019 10:29:35 +0200
Markus Armbruster <armbru@redhat.com> wrote:
> Aleksandar Markovic <aleksandar.m.mail@gmail.com> writes:
>
> > On May 29, 2019 5:09 PM, "Markus Armbruster" <armbru@redhat.com> wrote:
> >>
> >> When scripts/get_maintainer.pl reports something like
> >>
> >> John Doe <jdoe@example.org> (maintainer:Overall)
> >>
> >> the user is left to wonder *which* of our three "Overall" sections
> >> applies. We have three, one each under "Guest CPU cores (TCG)",
> >> "Guest CPU Cores (KVM)", and "Overall usermode emulation".
> >>
> >> Rename sections under
> >>
> >> * "Guest CPU cores (TCG)" from "FOO" to "FOO CPU cores (TCG)"
> >>
> >> * "Guest CPU Cores (KVM)" from "FOO" to "FOO CPU cores (KVM)"
> >>
> >> * "Guest CPU Cores (Xen)" from "FOO" to "FOO CPU cores (Xen)"
> >>
> >
> > In its essence definitely not a bad idea, but I must admit I tend to agree
> > with Philippe the new titles sound confusing, odd, artificial. Perhaps the
> > better alternative could be:
> >
> > “FOO TCG guest”
> > “FOO KVM guest”
> > “FOO Xen guest”
>
> Other suggestions mentioned so far:
>
> "FOO CPUs (TCG)"
> "TCG FOO CPUs"
>
> and same for KVM and Xen.
>
> I guess mentioning target first, accelerator second, no parenthesis
> makes sense. That leaves "guest" vs. "CPUs". Which one's closer to the
> truth?
'CPUs' makes more sense to me; 'guest' would also include
(architecture-specific) emulated devices.
>
> >> * "Architecture support" from "FOO" to "FOO general architecture
> >> support"
> >>
> >
> > Here we have a kind of strange situation with S390 architecture - it is the
> > only one present in this way in MAINTAINERS. Othrr than that, your new
> > wording looks fine to me.
>
> Yes, it's odd. But it's what works for the S390 maintainers.
Yes. I basically integrate all s390 stuff, including pull requests from
others. I'm more wondering why other architectures don't do that as
well :) Different setup, I guess.
next prev parent reply other threads:[~2019-06-03 9:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 15:08 [Qemu-devel] [PATCH 0/3] MAINTAINERS: Clean up and improve section headlines Markus Armbruster
2019-05-29 15:08 ` [Qemu-devel] [PATCH 1/3] MAINTAINERS: Drop redundant L: qemu-devel@nongnu.org Markus Armbruster
2019-05-29 15:52 ` Philippe Mathieu-Daudé
2019-05-29 19:09 ` Markus Armbruster
2019-05-29 15:08 ` [Qemu-devel] [PATCH 2/3] MAINTAINERS: Improve section headlines Markus Armbruster
2019-05-29 15:16 ` Eric Blake
2019-05-29 15:56 ` Philippe Mathieu-Daudé
2019-05-29 19:09 ` Markus Armbruster
2019-05-29 16:03 ` Philippe Mathieu-Daudé
2019-05-29 19:16 ` Markus Armbruster
2019-05-30 22:40 ` Aleksandar Markovic
2019-06-03 8:29 ` Markus Armbruster
2019-06-03 9:35 ` Cornelia Huck [this message]
2019-05-31 3:36 ` Stafford Horne
2019-06-03 8:32 ` Markus Armbruster
2019-06-03 8:45 ` Philippe Mathieu-Daudé
2019-06-04 10:33 ` Stafford Horne
2019-06-06 17:01 ` Markus Armbruster
2019-06-06 20:56 ` Stafford Horne
2019-05-29 15:08 ` [Qemu-devel] [PATCH 3/3] MAINTAINERS: Polish headline decorations 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=20190603113518.4cce7e76.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=aleksandar.m.mail@gmail.com \
--cc=armbru@redhat.com \
--cc=philmd@redhat.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).