qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
	qemu-devel@nongnu.org, Stephen Warren <swarren@wwwdotorg.org>
Subject: Re: [Qemu-devel] [PULL 31/32] MAINTAINERS: add all-match entry for qemu-devel@
Date: Tue, 9 Feb 2016 16:01:30 +0100	[thread overview]
Message-ID: <56B9FF4A.8020400@redhat.com> (raw)
In-Reply-To: <87r3gmhu73.fsf@blackfin.pond.sub.org>



On 09/02/2016 14:47, Markus Armbruster wrote:
>> >                                                The fallback now relies
>> > on finding a real person in MAINTAINERS, not just a mailing list for
> ... in fact all lists now are.  Entries with L: and without M:
> 
>     Maintained: LINUX, POSIX, i386 target
>     Odd fixes: GDB stub
>     Orphan: Gumstix, Mipssim, Stable 0.10, Stable 0.14, Stable 0.15

Not Stable 0.15 actually.

> For these, we now fall back to git.  Intentional?

Yes, intentional.  They are other instances of qemu-devel@ or, for
Gumstix, qemu-arm@.  For some of them it may make sense to give them an
M too, for stable versions we probably should drop them.

> If yes, mention it in the commit message.

It is mentioned.  For gumstix, it says sub-community right after where
you cut it. :) "The fallback now relies on finding a real person in
MAINTAINERS, not just a mailing list for the relevant sub-community".

For others, there's no reason why it should be different from the
catch-all entry.

> If no, the easiest fix is to give them an M, if we can find a willing
> victim.
> 
> Aside: we also have entries with neither L: nor M:
> 
>     Orphan: LSI53C895A, M68K, an5206, dummy_m68k, mcf5208
> 
> Odd.

Not too odd considering they're Orphan. :)  In fact the above entries
could have their L removed too (apart from Gumstix again).

Paolo

  reply	other threads:[~2016-02-09 15:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 12:13 [Qemu-devel] [PULL v2 00/32] Misc changes for 2016-02-08 Paolo Bonzini
2016-02-09 12:13 ` [Qemu-devel] [PULL 02/32] memory: RCU ram_list.dirty_memory[] for safe RAM hotplug Paolo Bonzini
2016-02-10 16:56   ` Leon Alrae
2016-02-10 17:01     ` Paolo Bonzini
2016-02-09 12:13 ` [Qemu-devel] [PULL 08/32] hw: Add support for LSI SAS1068 (mptsas) device Paolo Bonzini
2016-02-09 12:13 ` [Qemu-devel] [PULL 29/32] docs/memory.txt: Improve list of different memory regions Paolo Bonzini
2016-02-09 12:13 ` [Qemu-devel] [PULL 30/32] target-i386: fix PSE36 mode Paolo Bonzini
2016-02-09 12:13 ` [Qemu-devel] [PULL 31/32] MAINTAINERS: add all-match entry for qemu-devel@ Paolo Bonzini
2016-02-09 13:47   ` Markus Armbruster
2016-02-09 15:01     ` Paolo Bonzini [this message]
2016-02-09 15:24       ` Markus Armbruster
2016-02-09 15:27         ` Peter Maydell
2016-02-09 12:13 ` [Qemu-devel] [PULL 32/32] qemu-char, io: fix ordering of arguments for UDP socket creation Paolo Bonzini
2016-02-09 14:20 ` [Qemu-devel] [PULL v2 00/32] Misc changes for 2016-02-08 Peter Maydell
2016-02-09 14:41   ` Paolo Bonzini
2016-02-09 17:01     ` Richard Henderson

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=56B9FF4A.8020400@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=swarren@wwwdotorg.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).