qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@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, 09 Feb 2016 16:24:45 +0100	[thread overview]
Message-ID: <8737t1ewjm.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <56B9FF4A.8020400@redhat.com> (Paolo Bonzini's message of "Tue, 9 Feb 2016 16:01:30 +0100")

Paolo Bonzini <pbonzini@redhat.com> writes:

> 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.

Oops, it's Stable 1.0.

>> 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".

Yes, that sentence technically covers it, but I find the paragraph
confusing all the same.  Two ways to get my R-by:

1. Split the patch in two: part 1 is the get_maintainer.pl modification,
   part 2 is the MAINTAINERS update.  Each part does just one thing
   then, which allows simple commit messages.  That's what I'd do.

2. Keep the patch as is, but improve the commit message.  Here's my try:

    MAINTAINERS: Fall back to git unless we have a human, add qemu-devel@

    From: Stephen Warren <swarren@wwwdotorg.org>

    Add an entry to MAINTAINERS that matches every patch, and requests the
    user send patches to qemu-devel@nongnu.org.

    It's not 100% obvious to project newcomers that all patches should
    be sent there; get_maintainer.pl doesn't say so, and since it
    mentions other lists to CC, the wording "the list" from the
    SubmitAPatch wiki page can be taken to mean only those lists, not
    the main list too.

    The F: entries were taken from a similar entry in the Linux kernel.

    On its own, this would break fallback to git, because now every file
    has a maintainer of sorts.  Modify get_maintainer.pl so that mailing
    lists (L: lines) no longer prevent the fallback, only humans (M:
    entries).  This portion of the patch was suggested by
    pbonzini@redhat.com.

    Several pre-existing entries have a list but no human.  These now
    fall back to git.  That's a feature.

    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Cc: Markus Armbruster <armbru@redhat.com>
    Cc: John Snow <jsnow@redhat.com>
    Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
    Message-Id: <1454987065-12961-1-git-send-email-swarren@wwwdotorg.org>
    [Commit message tweaked]
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
    Reviewed-by: Markus Armbruster <armbru@redhat.com>

In addition, consider changing the "All patches CC here" line to "All
patches must be sent to this mailing list".

> 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:24 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
2016-02-09 15:24       ` Markus Armbruster [this message]
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=8737t1ewjm.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@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).