From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] posting patches in pull requests (was Re: [PATCH 08/29] cpu: Add qemu_for_each_cpu())
Date: Thu, 02 May 2013 19:09:00 +0200 [thread overview]
Message-ID: <51829DAC.5020807@suse.de> (raw)
In-Reply-To: <CAFEAcA_bQbtV=OmX=UytJVGURo0zYqeBsPP6fs=LNuABZZqXDA@mail.gmail.com>
Am 02.05.2013 18:08, schrieb Peter Maydell:
> On 2 May 2013 16:59, Andreas Färber <afaerber@suse.de> wrote:
>> Am 02.05.2013 16:57, schrieb Peter Maydell:
>>> Wow, you trust get_maintainer.pl that much? IME it
>>> tends to give a huge pile of useless cc suggestions.
>>
>> Useless? It's based on MAINTAINERS, which I expect maintainers to keep
>> up-to-date if they no longer want to maintain something. It's rather
>> that new files don't get entries and thus too few CCs at times IME.
>
> The ccs based on MAINTAINERS are fine -- it's the random
> extras it picks based on other people who've made patches
> to the same files in the past that are usually wrong.
> For example I tried running it on a patch to MAINTAINERS
> itself, and it suggested ccing you, Alex, Stefan H,
> Peter Crosthwaite and Edgar, which is a random mishmash
> and doesn't include the key person you actually need
> to CC, ie Anthony.
That's why Gerd correctly wrote scripts/get_maintainer.pl
--nogit-fallback - it doesn't do what you claim, although the default does.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-05-02 17:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 13:51 [Qemu-devel] posting patches in pull requests (was Re: [PATCH 08/29] cpu: Add qemu_for_each_cpu()) Michael S. Tsirkin
2013-05-02 14:09 ` Peter Maydell
2013-05-02 14:17 ` Michael S. Tsirkin
2013-05-02 14:21 ` Peter Maydell
2013-05-02 14:22 ` Michael S. Tsirkin
2013-05-02 14:46 ` Gerd Hoffmann
2013-05-02 14:57 ` Peter Maydell
2013-05-02 15:59 ` Andreas Färber
2013-05-02 16:08 ` Peter Maydell
2013-05-02 16:11 ` Michael S. Tsirkin
2013-05-02 17:09 ` Andreas Färber [this message]
2013-05-02 18:15 ` Anthony Liguori
2013-05-02 15:01 ` Stefan Hajnoczi
2013-05-02 15:30 ` Paolo Bonzini
2013-05-02 15:33 ` Peter Maydell
2013-05-02 15:52 ` Anthony Liguori
2013-05-02 15:55 ` Peter Maydell
2013-05-02 16:06 ` Michael S. Tsirkin
2013-05-02 16:59 ` Paolo Bonzini
2013-05-02 18:19 ` Anthony Liguori
2013-05-03 0:15 ` Peter Crosthwaite
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=51829DAC.5020807@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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.