From: Michael Tokarev <mjt@tls.msk.ru>
To: Thomas Huth <thuth@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Don Slutz <dslutz@verizon.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] get_maintainer.pl: Remove the --git-chief-penguins option
Date: Wed, 10 Dec 2014 11:47:59 +0300 [thread overview]
Message-ID: <548808BF.20407@msgid.tls.msk.ru> (raw)
In-Reply-To: <20141204125909.03040aaa@oc7435384737.ibm.com>
04.12.2014 14:59, Thomas Huth wrote:
>>
>> Ping?
>
> Ping again
Thomas, we was in freeze trying to get 2.2 out of the door.
During this time I didn't process -trivial patches, to not
pollute incoming changes stream even further.
Your patch for some reason does not apply to current
state of get_maintainer.pl script, failing this hunk:
>>>> - foreach my $chief (@penguin_chief) {
>>>> - if ($chief =~ m/^(.*):(.*)/) {
>>>> - my $email_address;
>>>> -
>>>> - $email_address = format_email($1, $2, $email_usename);
>>>> - if ($email_git_penguin_chiefs) {
>>>> - push(@email_to, [$email_address, 'chief penguin']);
>>>> - } else {
>>>> - @email_to = grep($_->[0] !~ /${email_address}/, @email_to);
>>>> - }
>>>> - }
>>>> - }
>>>> -
I didn't look at the details, because this is
a trivial delete of a block of code, so I just
deleted it manually.
So I applied your patch now.
Note there's one more reference to penguin chief
left in the code, in get_maintainer_role function.
I don't think it is wrong.
Thanks,
/mjt
prev parent reply other threads:[~2014-12-10 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 12:28 [Qemu-devel] [PATCH] get_maintainer.pl: Remove the --git-chief-penguins option Thomas Huth
2014-10-22 19:16 ` Don Slutz
2014-11-03 12:50 ` Thomas Huth
2014-12-04 11:59 ` Thomas Huth
2014-12-10 8:47 ` Michael Tokarev [this message]
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=548808BF.20407@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=dslutz@verizon.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@linux.vnet.ibm.com \
/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).