devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Guru Das Srinagesh <quic_gurus@quicinc.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Nicolas Schier <nicolas@fjasle.eu>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Kees Cook <keescook@chromium.org>,
	Bjorn Andersson <andersson@kernel.org>,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	Will Deacon <will@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	quic_pkondeti@quicinc.com
Cc: linux-kernel@vger.kernel.org, kernel@quicinc.com,
	workflows@vger.kernel.org, tools@linux.kernel.org,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 1/1] scripts: Add add-maintainer.py
Date: Mon, 28 Aug 2023 10:21:32 +0200	[thread overview]
Message-ID: <2efba6b3-2399-9deb-d0ce-78f7b5e12f30@linaro.org> (raw)
In-Reply-To: <141b9fcab2208ace3001df4fc10e3dfd42b9f5d9.1693037031.git.quic_gurus@quicinc.com>

On 26/08/2023 10:07, Guru Das Srinagesh wrote:
> This script runs get_maintainer.py on a given patch file (or multiple
> patch files) and adds its output to the patch file in place with the
> appropriate email headers "To: " or "Cc: " as the case may be. These new
> headers are added after the "From: " line in the patch.
> 
> Currently, for a single patch, maintainers and reviewers are added as
> "To: ", mailing lists and all other roles are added as "Cc: ".
> 
> For a series of patches, however, a set-union scheme is employed in
> order to solve the all-too-common problem of ending up sending only
> subsets of a patch series to some lists, which results in important
> pieces of context such as the cover letter (or other patches in the
> series) being dropped from those lists. This scheme is as follows:
> 
> - Create set-union of all maintainers and reviewers from all patches and
>   use this to do the following per patch:
>   - add only that specific patch's maintainers and reviewers as "To: "
>   - add the other maintainers and reviewers from the other patches as "Cc: "
> 
> - Create set-union of all mailing lists corresponding to all patches and
>   add this to all patches as "Cc: "
> 
> - Create set-union of all other roles corresponding to all patches and
>   add this to all patches as "Cc: "
> 
> Please note that patch files that don't have any "Maintainer"s or
> "Reviewers" explicitly listed in their `get_maintainer.pl` output will

So before you will ignoring the reviewers, right? One more reason to not
get it right...

> not have any "To: " entries added to them; developers are expected to
> manually make edits to the added entries in such cases to convert some
> "Cc: " entries to "To: " as desired.
> 
> The script is quiet by default (only prints errors) and its verbosity
> can be adjusted via an optional parameter.
> 
> Signed-off-by: Guru Das Srinagesh <quic_gurus@quicinc.com>
> ---
>  MAINTAINERS               |   5 ++
>  scripts/add-maintainer.py | 164 ++++++++++++++++++++++++++++++++++++++
>  2 files changed, 169 insertions(+)
>  create mode 100755 scripts/add-maintainer.py
> 

I do not see the benefits of this script. For me - it's unnecessarily
more complicated instead of my simple bash function which makes
everything one command less than here.
One more thing to maintain.

I don't see the benefits of this for newcomers, either. They should use
b4. b4 can do much, much more, so anyone creating his workflow should
start from b4, not from this script.

Best regards,
Krzysztof


  parent reply	other threads:[~2023-08-28  8:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-26  8:07 [PATCH v3 0/1] Add add-maintainer.py script Guru Das Srinagesh
2023-08-26  8:07 ` [PATCH v3 1/1] scripts: Add add-maintainer.py Guru Das Srinagesh
2023-08-27 16:44   ` Randy Dunlap
2023-08-28 16:45     ` Guru Das Srinagesh
2023-08-28  8:14   ` Jani Nikula
2023-08-28 13:35     ` Bjorn Andersson
2023-08-28 13:48       ` Geert Uytterhoeven
2023-08-28 15:14         ` Vlastimil Babka
2023-08-28 15:23           ` Krzysztof Kozlowski
2023-08-28 16:50             ` Bjorn Andersson
2023-08-29  7:38               ` Jani Nikula
2023-08-28 16:50     ` Guru Das Srinagesh
2023-08-28  8:21   ` Krzysztof Kozlowski [this message]
2023-08-28 17:56     ` Guru Das Srinagesh
2023-08-28 17:59       ` Krzysztof Kozlowski
2023-08-28 19:41         ` Mark Brown
2023-08-28 19:45           ` Krzysztof Kozlowski
2023-08-29 23:16             ` Guru Das Srinagesh
2023-08-30  7:11               ` Krzysztof Kozlowski
2023-08-30 11:22               ` Mark Brown
2023-08-30 14:16                 ` Jeff Johnson
2023-09-27  4:51     ` Pavan Kondeti
2023-09-27 22:44       ` Guru Das Srinagesh
2023-09-26 12:02   ` Pavan Kondeti
2023-09-27  4:54     ` Pavan Kondeti
2023-09-27 22:47     ` Guru Das Srinagesh

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=2efba6b3-2399-9deb-d0ce-78f7b5e12f30@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --cc=kernel@quicinc.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    --cc=quic_gurus@quicinc.com \
    --cc=quic_pkondeti@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=tools@linux.kernel.org \
    --cc=will@kernel.org \
    --cc=workflows@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 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).