From: Gerd Hoffmann <kraxel@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>,
Markus Armbruster <armbru@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] get_maintainer.pl: Default to --no-git-fallback
Date: Tue, 21 Oct 2014 13:09:19 +0200 [thread overview]
Message-ID: <1413889759.14632.17.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <544556A1.3020405@redhat.com>
On Mo, 2014-10-20 at 20:38 +0200, Paolo Bonzini wrote:
> 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).
How about making "get_maintainer.pl --git-fallback" actually do what it
says? Right now git it *not* used as fallback, it goes to git log
unconditionally, even if there are hits in MAINTAINERS ...
Different behavior depending on whenever stdout is a tty or not should
be doable too.
cheers,
Gerd
next prev parent reply other threads:[~2014-10-21 11:09 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 [this message]
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
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=1413889759.14632.17.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=armbru@redhat.com \
--cc=mst@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).