qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Amit Shah <amit.shah@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: fix pattern for PC
Date: Mon, 29 Jun 2015 12:54:35 +0200	[thread overview]
Message-ID: <559123EB.90104@redhat.com> (raw)
In-Reply-To: <CAFEAcA8vetdpdq8kZb0fgDn1=8MNGQD+kF+PAogucH__6idFtQ@mail.gmail.com>

On 06/29/15 12:42, Peter Maydell wrote:
> On 29 June 2015 at 11:23, Laszlo Ersek <lersek@redhat.com> wrote:
>> On 06/29/15 12:00, Peter Maydell wrote:
>>> On 29 June 2015 at 10:54, Michael S. Tsirkin <mst@redhat.com> wrote:
>>>> Looks like hw/i386/ does not work, hw/i386/*
>>>> seems to work better.
>>>
>>> This is kind of vague... The documentation at the top
>>> of MAINTAINERS says the difference is that "hw/i386/"
>>> means "all files in and below hw/i386/", whereas
>>> "hw/i386/*" means "all files in hw/i386, but not below"
>>> (so won't match anything in hw/i386/kvm/ or hw/i386/xen/).
>>> Is this the effect you're trying to achieve? It would
>>> be nice to mention the symptoms of the problem this patch
>>> is fixing in the commit message...
>>
>> Assume I format the patch series:
>>
>>   http://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg06677.html
>>
>> into a single file, with
>>
>>   git format-patch --notes --cover-letter --numbered --stdout
>>
>> and then run scripts/get_maintainer.pl on the resultant patch series file.
>>
>> Before this patch, I get:
>>
>>   Paolo Bonzini <pbonzini@redhat.com> (maintainer:X86)
>>   Richard Henderson <rth@twiddle.net> (maintainer:X86)
>>   Eduardo Habkost <ehabkost@redhat.com> (maintainer:X86)
>>   "Michael S. Tsirkin" <mst@redhat.com> (supporter:PC)
>>
>> Since Michael was listed at the bottom of that list, I didn't CC him. (I
>> wanted to give him a breather after my many PXB iterations.)
>>
>> Turns out that wasn't a good choice. With this patch for MAINTAINERS in
>> place, the script reports Michael at the top:
>>
>>   "Michael S. Tsirkin" <mst@redhat.com> (supporter:PC)
>>   Paolo Bonzini <pbonzini@redhat.com> (maintainer:X86)
>>   Richard Henderson <rth@twiddle.net> (maintainer:X86)
>>   Eduardo Habkost <ehabkost@redhat.com> (maintainer:X86)
>>
>> Maybe I should have considered something else than just the ordering of
>> the names in the list, not sure...
>>
>> Hm, yes, this is at least partly (if not fully) my fault. MAINTAINERS says
>>
>>         S: Status, one of the following:
>>            Supported:   Someone is actually paid to look after this.
>>            Maintained:  Someone actually looks after it.
>>
>> I didn't realize this distinction, and I also didn't realize that
>> "supporter" and "maintainer" were derived directly from "Supported" and
>> "Maintained".
>>
>> It would be helpful if developers with more jurisdiction (according to
>> the Supported / Maintained / Odd Fixes classification) were listed
>> higher in the output.
> 
> Mmm. If this is what we're trying to fix then messing with
> our MAINTAINERS file seems like the wrong thing.
> 
> Personally I think that the best approach would be just to
> cc everybody that get_maintainers.pl says is a maintainer
> or supporter; they're in the file because they *want* this
> email, after all...

Are you sure? See commit c6561586.

... Hm, although, that's specifically for the case when the MAINTAINERS
file has failed to help. So you can indeed say that whenever MAINTAINERS
matches, those people *all* want to be Cc'd.

> If your patchset touches two areas then
> that doesn't mean it's OK to drop a 'maintainer' email for
> area 2 just because area 1 happens to have two or three
> 'supporter' emails listed.

I didn't omit some Cc's because of area mismatches. I just wanted to
avoid spamming people, and took only the top of the list (Paolo). In the
future I'll include everyone. (Hopefully that won't lead to all people
on the Cc list thinking that someone else on that long Cc list should
review the patch...)

Thanks
Laszlo

      reply	other threads:[~2015-06-29 10:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29  9:54 [Qemu-devel] [PATCH] MAINTAINERS: fix pattern for PC Michael S. Tsirkin
2015-06-29 10:00 ` Peter Maydell
2015-06-29 10:23   ` Laszlo Ersek
2015-06-29 10:42     ` Peter Maydell
2015-06-29 10:54       ` Laszlo Ersek [this message]

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=559123EB.90104@redhat.com \
    --to=lersek@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).