[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZOz4XtX3DFRQpvQY@finisterre.sirena.org.uk>
Date: Mon, 28 Aug 2023 20:41:18 +0100
From: Mark Brown <broonie@...nel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Masahiro Yamada <masahiroy@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Nicolas Schier <nicolas@...sle.eu>,
Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
Kees Cook <keescook@...omium.org>,
Bjorn Andersson <andersson@...nel.org>, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, Will Deacon <will@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
quic_pkondeti@...cinc.com, linux-kernel@...r.kernel.org,
kernel@...cinc.com, workflows@...r.kernel.org,
tools@...ux.kernel.org, devicetree@...r.kernel.org,
linux-arm-msm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH v3 1/1] scripts: Add add-maintainer.py
On Mon, Aug 28, 2023 at 07:59:54PM +0200, Krzysztof Kozlowski wrote:
> On 28/08/2023 19:56, Guru Das Srinagesh wrote:
> > Your function adds mailing lists also in "To:" which is not ideal, in my view.
> > You've mentioned before that To or Cc doesn't matter [1] which I disagree
> > with: it doesn't matter, why does Cc exist as a concept at all?
> To/Cc does not matter when sending new patch, because maintainers know
> they are maintainers of which parts. I know what I handle.
That might be true for you (and also is for me) but I know there are
people who pay attention to if they're in the To: for various reasons, I
gather it's mostly about triaging their emails and is especially likely
in cases where trees have overlaps in the code they cover.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists