From: Guru Das Srinagesh <quic_gurus@quicinc.com>
To: Pavan Kondeti <quic_pkondeti@quicinc.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Guru Das Srinagesh <quic_gurus@quicinc.com>,
Nick Desaulniers <ndesaulniers@google.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
Nicolas Schier <nicolas@fjasle.eu>,
"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>,
<u.kleine-koenig@pengutronix.de>, <linux-kernel@vger.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 v2 1/1] scripts: Add add-maintainer.py
Date: Thu, 10 Aug 2023 11:52:37 -0700 [thread overview]
Message-ID: <20230810185237.GB31860@quicinc.com> (raw)
In-Reply-To: <44afa9e4-9aaa-4a80-b2a9-57d0bf14b6e0@quicinc.com>
On Aug 03 2023 14:34, Pavan Kondeti wrote:
> On Thu, Aug 03, 2023 at 01:23:16AM -0700, Guru Das Srinagesh wrote:
> > This script runs get_maintainer.py on a given patch file 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 are added as "To: ", mailing
> > lists and all other roles are addded as "Cc: ".
> >
> > For a series of patches, however, a set-union scheme is employed in
> > order to solve the all-too-common problem of sending subsets of a patch
> > series to some lists, which results in important pieces of context such
> > as the cover letter being dropped. This scheme is as follows:
> > - 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: "
> > - Create set-union of all maintainers from all patches and use this to
> > do the following per patch:
> > - add only that specific patch's maintainers as "To: ", and
> > - the other maintainers from the other patches as "Cc: "
> >
>
> Thanks. I have tested this logic by running this script on two patches
> from different subsystems. It does what it says.
Thanks for testing this v2!
>
> > Please note that patch files that don't have any "Maintainer"s
> > explicitly listed in their `get_maintainer.pl` output will 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>
> > ---
> > scripts/add-maintainer.py | 113 ++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 113 insertions(+)
> > create mode 100755 scripts/add-maintainer.py
> >
>
> Do you need to update MAINTAINERS file?
Noted.
>
[...]
>
> Few minor issues from my limited testing:
>
> - It is very unlikely, but for whatever reason if "From:" is present in
> the patch (commit description), this script bails out. Pls try running
> this script on the current patch. May be you should also look for a
> proper email address on this line.
>
> - When this script is run on a file (get_maintainer.pl allows this), it
> throws a runtime warning. may be good to bail out much earlier.
>
> - When this script runs on a non-existent file, it does not bail out
> early.
Will fix these.
Thank you.
Guru Das.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-10 18:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 8:23 [PATCH v2 0/1] Add add-maintainer.py script Guru Das Srinagesh
2023-08-03 8:23 ` [PATCH v2 1/1] scripts: Add add-maintainer.py Guru Das Srinagesh
2023-08-03 9:04 ` Pavan Kondeti
2023-08-10 18:52 ` Guru Das Srinagesh [this message]
2023-08-23 15:14 ` Nicolas Schier
2023-08-24 21:44 ` Guru Das Srinagesh
2023-08-25 11:44 ` Nicolas Schier
2023-08-25 17:00 ` Guru Das Srinagesh
2023-08-27 5:52 ` Nicolas Schier
2023-08-03 9:16 ` [PATCH v2 0/1] Add add-maintainer.py script Neil Armstrong
2023-08-10 18:49 ` Guru Das Srinagesh
2023-08-19 2:23 ` Guru Das Srinagesh
2023-08-10 18:55 ` Guru Das Srinagesh
2023-08-15 21:06 ` Krzysztof Kozlowski
2023-08-16 17:15 ` Guru Das Srinagesh
2023-08-18 8:33 ` Neil Armstrong
2023-08-19 1:48 ` Guru Das Srinagesh
2023-08-18 8:43 ` Krzysztof Kozlowski
2023-08-18 19:46 ` Bjorn Andersson
2023-08-19 7:50 ` Krzysztof Kozlowski
2023-08-19 1:33 ` Guru Das Srinagesh
2023-08-19 7:53 ` Krzysztof Kozlowski
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=20230810185237.GB31860@quicinc.com \
--to=quic_gurus@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.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_pkondeti@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=will@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).