From: Tom Rini <trini@konsulko.com>
To: Casey Connolly <casey.connolly@linaro.org>
Cc: Marek Vasut <marek.vasut+renesas@mailbox.org>, u-boot@lists.denx.de
Subject: Re: [PATCH] get_maintainer.pl: tighten up git contributors cc list
Date: Wed, 1 Jul 2026 11:24:29 -0600 [thread overview]
Message-ID: <20260701172429.GL749385@bill-the-cat> (raw)
In-Reply-To: <20260701095003.212997-1-casey.connolly@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1974 bytes --]
On Wed, Jul 01, 2026 at 11:50:01AM +0200, Casey Connolly wrote:
> get_maintainer in U-Boot is configured to include contributors and patch
> reviewers from the git history in the CC list, going back 1 year if they
> have contributed more than 5% of the patches.
>
> This is well suited to some core U-Boot code that has a long history and
> doesn't get much love from any dedicated maintainer but for newer code
> and board code in general as well as defconfigs it can be frustrating
> for some contributors who do not wish to be CC'd on patches as well as a
> general issue when dead emails are included.
>
> While it would be desirable to just remove the --git flag and encourage
> those interested to configure lei or just add themselves to MAINTAINERS
> it perhaps makes more sense to phase it out gradually.
>
> As a first step, reduce the time period that will be checked in the git
> history from 1 year to 6 months, this still offers plenty of leeway for
> contributions to the last 1/2 U-Boot releases. In addition, bump up the
> required percentage of contributions from 5% to 15% and reduce the limit
> on the number of "git maintainers" (i.e. unique S-o-b/A-b/R-b tags) from
> 5 to 2.
>
> These changes should reduce the size of CC lists while still including
> recent active contributors.
>
> Signed-off-by: Casey Connolly <casey.connolly@linaro.org>
> ---
> Cc: Marek Vasut <marex@denx.de>
> ---
> .get_maintainer.conf | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/.get_maintainer.conf b/.get_maintainer.conf
> index f916cfbe480e..302fcee9699f 100644
> --- a/.get_maintainer.conf
> +++ b/.get_maintainer.conf
> @@ -1 +1,6 @@
> ---find-maintainer-files --git --maintainer-path=.
> +--find-maintainer-files
> +--git
> +--git-min-percent 15
> +--git-since 6-months-ago
> +--git-max-maintainers 2
> +--maintainer-path=.
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-07-01 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 9:50 [PATCH] get_maintainer.pl: tighten up git contributors cc list Casey Connolly
2026-07-01 17:24 ` Tom Rini [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=20260701172429.GL749385@bill-the-cat \
--to=trini@konsulko.com \
--cc=casey.connolly@linaro.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=u-boot@lists.denx.de \
/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.