From: Guru Das Srinagesh <quic_gurus@quicinc.com>
To: Pavan Kondeti <quic_pkondeti@quicinc.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
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>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] scripts: Add add-maintainer.py
Date: Wed, 2 Aug 2023 15:46:58 -0700 [thread overview]
Message-ID: <20230802224658.GA17567@quicinc.com> (raw)
In-Reply-To: <63764b84-3ebd-4081-836f-4863af196228@quicinc.com>
On Aug 02 2023 15:35, Pavan Kondeti wrote:
> Thanks Guru for submitting this script. In my limited testing, I don't
> find any issues. It works as expected.
Great! Thank you so much for testing this script.
> If I run this script on a series which spans across different lists,
> there is a possiblity that we send partial series to certain lists. What
> is the best way to deal with this? one way is to include union of all
> lists in CC while sending the series with primary maintainer in TO. Can
> the script print those values for easier workflow?
Thanks for bringing this up - I was hoping to start a conversation on this.
Your suggestion seems logical to me. I can update v2 of this script adding an
`-a` flag that will add all maintainers to all patches following the scheme of
gathering the union of all maintainers, lists and "others" separately.
Hoping to get feedback from other maintainers on this point as well. Should I
expand the audience of this patch some more? I addressed this to whomever
`get_maintainer.pl -f ./scripts/` listed, plus Bjorn.
Guru Das.
prev parent reply other threads:[~2023-08-02 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 4:54 [PATCH 0/1] Add add-maintainer.py script Guru Das Srinagesh
2023-08-02 4:54 ` [PATCH 1/1] scripts: Add add-maintainer.py Guru Das Srinagesh
2023-08-02 10:05 ` Pavan Kondeti
2023-08-02 22:46 ` Guru Das Srinagesh [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=20230802224658.GA17567@quicinc.com \
--to=quic_gurus@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=andersson@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=quic_pkondeti@quicinc.com \
/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