From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Thomas Monjalon <thomas@monjalon.net>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] devtools: disable fixes authors in get maintainers
Date: Tue, 2 Nov 2021 10:07:42 +0000 [thread overview]
Message-ID: <aecc00e7-d301-c3c6-5f87-08a4f65fa101@intel.com> (raw)
In-Reply-To: <20211101161904.49e4da0d@hermes.local>
On 11/1/2021 11:19 PM, Stephen Hemminger wrote:
> On Mon, 1 Nov 2021 13:35:33 +0000
> Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
>> 'get_maintainer.pl' by default returns authors that has fixes in
>> relevant code, to reduce the output only maintainers from MAINTAINERS
>> file, disabling fixes authors, by making '--no-fixes' default.
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Isn't it better to send to more people on patches rather than less.
> There could be cases where a patch reverts a change and the original
> author never gets notified after this.
>
> Could you give an example?
>
I already gave a sample on response to Thomas, can you please check there,
to not fork the same discussion.
Thanks,
ferruh
next prev parent reply other threads:[~2021-11-02 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 13:35 [dpdk-dev] [PATCH 1/2] devtools: remove ugly workaround from " Ferruh Yigit
2021-11-01 13:35 ` [dpdk-dev] [PATCH 2/2] devtools: disable fixes authors in " Ferruh Yigit
2021-11-01 22:20 ` Thomas Monjalon
2021-11-02 10:04 ` Ferruh Yigit
2021-11-02 11:28 ` Thomas Monjalon
2021-11-02 12:08 ` Ferruh Yigit
2021-11-01 23:19 ` Stephen Hemminger
2021-11-02 10:07 ` Ferruh Yigit [this message]
2022-01-13 11:35 ` [dpdk-dev] [PATCH 1/2] devtools: remove ugly workaround from " Thomas Monjalon
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=aecc00e7-d301-c3c6-5f87-08a4f65fa101@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).