From: "Michael S. Tsirkin" <mst@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] get_maintainer.pl: Default to --no-git-fallback
Date: Wed, 22 Oct 2014 11:29:32 +0300 [thread overview]
Message-ID: <20141022082932.GB7797@redhat.com> (raw)
In-Reply-To: <871tq0jzti.fsf@blackfin.pond.sub.org>
On Wed, Oct 22, 2014 at 10:03:53AM +0200, Markus Armbruster wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
>
> > On Wed, Oct 22, 2014 at 09:01:24AM +0200, Markus Armbruster wrote:
> >> "Michael S. Tsirkin" <mst@redhat.com> writes:
> >>
> >> > On Tue, Oct 21, 2014 at 03:34:46PM +0200, Markus Armbruster wrote:
> >> >> Paolo Bonzini <pbonzini@redhat.com> writes:
> >> >>
> >> >> > On 10/20/2014 04:15 PM, Michael S. Tsirkin wrote:
> >> >> >> What do you want to happen in this case?
> >> >> >> Won't this cause even more patches to fall to the floor?
> >> >> >>
> >> >> >> The benefit seems marginal, the risk high.
> >> >> >
> >> >> > I agree with Michael.
> >> >> >
> >> >> > Can we detect if get_maintainer.pl is invoked as a cccmd, and in this
> >> >> > case default to --no-git-fallback? If it is invoked manually, I would
> >> >> > like to show the committers (I will then cherry pick the right ones).
> >> >>
> >> >> I don't like context-sensitive defaults. Too much magic.
> >> >>
> >> >> What about this: if get_maintainer.pl comes up empty, it points you to
> >> >> --git-fallback.
> >> >
> >> > This is exactly what it's doing now :)
> >>
> >> Nope. This is what it's doing now:
> >>
> >> $ scripts/get_maintainer.pl -f util/cutils.c
> >> Luiz Capitulino <lcapitulino@redhat.com> (commit_signer:1/2=50%)
> >> Eric Blake <eblake@redhat.com> (commit_signer:1/2=50%)
> >> Alexey Kardashevskiy <aik@ozlabs.ru> (commit_signer:1/2=50%)
> >> Laszlo Ersek <lersek@redhat.com> (commit_signer:1/2=50%)
> >> Amit Shah <amit.shah@redhat.com> (commit_signer:1/2=50%)
> >>
> >> A sufficiently seasoned contributor will spot the "commit_signer" tags,
> >> and the output as a hint to find people to copy. In this particular
> >> case, he'll recognize the hint is useless. Maybe he'll try something
> >> like --git-since 2010 or --git-blame then. I'd just peruse git-log.
> >>
> >> A less seasoned contributor will blindly copy all five.
> >
> > I give up. What's the correct answer?
> > I frankly don't know whom should one copy on this file.
> > Fabrice?
>
> Fabrice would be a textbook example of a useless cc.
>
> I'd pick based on the patch's contents. For instance, if it fixes a
> function that is used by block stuff only, try copying block
> maintainers. You get the idea. It's an art, not something a dumb
> script can do.
>
> An inexperienced contributor probably won't be able to find out whom to
> copy here. Making him send out five mostly useless copies is not a
> solution.
Maybe disable fallback just for utils:
+UTIL
+M: qemu-devel@nongnu.org
+S: Odd Fixes
+F: util/
> Don proposed adding a catchall maintainer, and Peter refined
> it to qemu-unmaintained@... This could serve as a formal cry "I have no
> idea who could review this, please help me".
>
> [...]
The list is a good idea. But I'd like a flag to avoid adding that
automatically. Call it --expert or whatever. So need to write some
code in get_maintainer.
--
MST
next prev parent reply other threads:[~2014-10-22 8:26 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 9:19 [Qemu-devel] [PATCH] get_maintainer.pl: Default to --no-git-fallback Markus Armbruster
2014-10-20 12:27 ` Don Slutz
2014-10-20 14:04 ` Peter Maydell
2014-10-20 14:15 ` Michael S. Tsirkin
2014-10-20 14:19 ` Peter Maydell
2014-10-20 19:03 ` Michael S. Tsirkin
2014-10-20 20:10 ` Don Slutz
2014-10-20 21:07 ` Peter Maydell
2014-10-21 9:31 ` Markus Armbruster
2014-10-21 10:00 ` Michael S. Tsirkin
2014-10-21 12:22 ` Markus Armbruster
2014-10-21 12:38 ` Michael S. Tsirkin
2014-10-21 13:29 ` Markus Armbruster
2014-10-21 22:30 ` Michael S. Tsirkin
2014-10-22 6:39 ` Markus Armbruster
2014-10-22 7:01 ` Michael S. Tsirkin
2014-10-22 8:10 ` Thomas Huth
2014-10-22 8:18 ` Michael S. Tsirkin
2014-10-20 18:38 ` Paolo Bonzini
2014-10-21 11:09 ` Gerd Hoffmann
2014-10-21 11:15 ` Michael S. Tsirkin
2014-10-21 11:23 ` Gerd Hoffmann
2014-10-21 11:35 ` Michael S. Tsirkin
2014-10-21 13:34 ` Markus Armbruster
2014-10-21 13:39 ` Paolo Bonzini
2014-10-21 13:46 ` Kirill Batuzov
2014-10-21 22:31 ` Michael S. Tsirkin
2014-10-22 7:01 ` Markus Armbruster
2014-10-22 7:12 ` Michael S. Tsirkin
2014-10-22 7:45 ` Paolo Bonzini
2014-10-22 8:03 ` Markus Armbruster
2014-10-22 8:29 ` Michael S. Tsirkin [this message]
2014-10-22 19:25 ` Don Slutz
2014-10-21 6:22 ` Thomas Huth
2014-10-21 9:19 ` Markus Armbruster
2014-10-21 13:40 ` Kirill Batuzov
2014-10-21 14:15 ` Markus Armbruster
2014-10-21 22:35 ` Michael S. Tsirkin
2014-10-20 15:06 ` Eric Blake
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=20141022082932.GB7797@redhat.com \
--to=mst@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@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).