qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: John Snow <jsnow@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: add all-match entry for qemu-devel@
Date: Mon, 8 Feb 2016 19:15:34 +0000	[thread overview]
Message-ID: <CAFEAcA_kfc5ZDL0cwX3cOPh-zg3NLc4J_K+WeomikF63KYZN-w@mail.gmail.com> (raw)
In-Reply-To: <56B8E6A8.8080506@wwwdotorg.org>

On 8 February 2016 at 19:04, Stephen Warren <swarren@wwwdotorg.org> wrote:
> qemu's get_maintainers.pl must be doing something different to the Linux
> kernel's version then, since IIRC the Linux kernel version always prints out
> recent contributors irrespective of whether maintainers were found, rather
> than as an alternative. I think if qemu's get_maintainers.pl acted in that
> way it would solve the problem my patch caused?

That difference from the kernel script's behaviour is deliberate, because
the attempt to list recent contributors tends to list a whole lot of
irrelevant people. So if there's a documented maintainer we prefer to
just list them, and not all the random other people looking at the git
logs drags up. Commit c6561586f0f8586 is where we changed the behaviour
of get_maintainer.pl and the commit message has some rationale.

thanks
-- PMM

  reply	other threads:[~2016-02-08 19:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 17:22 [Qemu-devel] [PATCH] MAINTAINERS: add all-match entry for qemu-devel@ Stephen Warren
2016-02-08  9:05 ` Markus Armbruster
2016-02-08 18:52   ` John Snow
2016-02-08 19:04     ` Stephen Warren
2016-02-08 19:15       ` Peter Maydell [this message]
2016-02-08 19:56         ` Paolo Bonzini

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=CAFEAcA_kfc5ZDL0cwX3cOPh-zg3NLc4J_K+WeomikF63KYZN-w@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --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).