qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>,
	"Anthony Liguori" <anthony@codemonkey.ws>,
	"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [Qemu-devel] posting patches in pull requests (was Re: [PATCH 08/29] cpu: Add qemu_for_each_cpu())
Date: Thu, 2 May 2013 19:11:04 +0300	[thread overview]
Message-ID: <20130502161104.GB14776@redhat.com> (raw)
In-Reply-To: <CAFEAcA_bQbtV=OmX=UytJVGURo0zYqeBsPP6fs=LNuABZZqXDA@mail.gmail.com>

On Thu, May 02, 2013 at 05:08:06PM +0100, Peter Maydell wrote:
> 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.

Just add --nogit then?

> 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.
> 
> The actual rule as far as I can tell for CCs is "if
> file is explicitly listed in MAINTAINERS, cc those people;
> otherwise CC either Blue and Aurelien [if a random
> target-* patch] or Anthony [everything else]; cc trivial
> if sufficiently small; also for bugfixes CC whoever wrote
> the commit you're fixing". get_maintainer.pl doesn't do
> that, so I just write CCs manually.
> 
> thanks
> -- PMM

You could also try to make get_maintainer.pl do what you want.
Well maybe beside trivial.

  reply	other threads:[~2013-05-02 16:11 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 [this message]
2013-05-02 17:09               ` Andreas Färber
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=20130502161104.GB14776@redhat.com \
    --to=mst@redhat.com \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=kraxel@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 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).