From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, corbet@lwn.net
Subject: Re: [PATCH net v2 0/7] MAINTAINERS: remove inactive folks from networking
Date: Thu, 14 Jan 2021 19:00:11 +0000 [thread overview]
Message-ID: <161065081111.20848.7577461351346623187.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210114014912.2519931-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Wed, 13 Jan 2021 17:49:05 -0800 you wrote:
> Hi!
>
> This series intends to remove some most evidently inactive maintainers.
>
> To make maintainers' lives easier we're trying to nudge people
> towards CCing all the relevant folks on patches, in an attempt
> to improve review rate. We have a check in patchwork which validates
> the CC list against get_maintainers.pl. It's a little awkward, however,
> to force people to CC maintainers who we haven't seen on the mailing
> list for years. This series removes from maintainers folks who didn't
> provide any tag (incl. authoring a patch) in the last 5 years.
> To ensure reasonable signal to noise ratio we only considered
> MAINTAINERS entries which had more than 100 patches fall under
> them in that time period.
>
> [...]
Here is the summary with links:
- [net,v2,1/7] MAINTAINERS: altx: move Jay Cliburn to CREDITS
https://git.kernel.org/netdev/net/c/93089de91e85
- [net,v2,2/7] MAINTAINERS: net: move Alexey Kuznetsov to CREDITS
https://git.kernel.org/netdev/net/c/09cd3f4683a9
- [net,v2,3/7] MAINTAINERS: vrf: move Shrijeet to CREDITS
https://git.kernel.org/netdev/net/c/5e62d124f75a
- [net,v2,4/7] MAINTAINERS: ena: remove Zorik Machulsky from reviewers
https://git.kernel.org/netdev/net/c/c41efbf2ad56
- [net,v2,5/7] MAINTAINERS: tls: move Aviad to CREDITS
https://git.kernel.org/netdev/net/c/0e4ed0b62b5a
- [net,v2,6/7] MAINTAINERS: ipvs: move Wensong Zhang to CREDITS
https://git.kernel.org/netdev/net/c/4f3786e01194
- [net,v2,7/7] MAINTAINERS: dccp: move Gerrit Renker to CREDITS
https://git.kernel.org/netdev/net/c/054c4610bd05
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-01-14 19:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 1:49 [PATCH net v2 0/7] MAINTAINERS: remove inactive folks from networking Jakub Kicinski
2021-01-14 1:49 ` [PATCH net v2 1/7] MAINTAINERS: altx: move Jay Cliburn to CREDITS Jakub Kicinski
2021-01-14 1:49 ` [PATCH net v2 2/7] MAINTAINERS: net: move Alexey Kuznetsov " Jakub Kicinski
2021-01-14 1:49 ` [PATCH net v2 3/7] MAINTAINERS: vrf: move Shrijeet " Jakub Kicinski
2021-01-14 1:49 ` [PATCH net v2 4/7] MAINTAINERS: ena: remove Zorik Machulsky from reviewers Jakub Kicinski
2021-01-14 1:49 ` [PATCH net v2 5/7] MAINTAINERS: tls: move Aviad to CREDITS Jakub Kicinski
2021-01-14 1:49 ` [PATCH net v2 6/7] MAINTAINERS: ipvs: move Wensong Zhang " Jakub Kicinski
2021-01-14 19:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-14 1:49 [PATCH net v2 7/7] MAINTAINERS: dccp: move Gerrit Renker " Jakub Kicinski
2021-01-14 1:49 ` Jakub Kicinski
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=161065081111.20848.7577461351346623187.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.