From: Nicolas Schier <nicolas@fjasle.eu>
To: Guru Das Srinagesh <quic_gurus@quicinc.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Andrew Morton <akpm@linux-foundation.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, 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: Sun, 27 Aug 2023 07:52:53 +0200 [thread overview]
Message-ID: <ZOrktcX1L6WHmLBi@fjasle.eu> (raw)
In-Reply-To: <20230825170001.GB22659@quicinc.com>
On Fri, Aug 25, 2023 at 10:00:01AM -0700 Guru Das Srinagesh wrote:
> On Aug 25 2023 13:44, Nicolas Schier wrote:
> > On Thu 24 Aug 2023 14:44:36 GMT, Guru Das Srinagesh wrote:
> > > > While testing, I thought that adding addresses without filtering-out duplicates
> > > > was odd; but as git-send-email does the unique filtering, it doesn't matter.
> > >
> > > Since I'm using `set()` in this script, the uniqueness is guaranteed here as
> > > well - there won't be any duplicates.
> >
> > I thought about patch files that already have 'To/Cc' headers (e.g.
> > 'git format-patch --to=... --cc=...' or by running add-maintainer.py
> > multiple times for updating the lists of recipients. The result is a
> > patch file with possible duplicated lines; but as written: it does
> > matter, effectively.
>
> Sorry, did you mean "does" or "does *not*"?
I'm sorry, "it doe not matter".
Nicolas
> I'll make sure to test v3 of this script out on patches that have To/Cc already
> included and also run it multiple times on the same patch (effectively the same
> thing).
>
> Thank you.
>
> Guru Das.
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Schier <nicolas@fjasle.eu>
To: Guru Das Srinagesh <quic_gurus@quicinc.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Andrew Morton <akpm@linux-foundation.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, 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: Sun, 27 Aug 2023 07:52:53 +0200 [thread overview]
Message-ID: <ZOrktcX1L6WHmLBi@fjasle.eu> (raw)
In-Reply-To: <20230825170001.GB22659@quicinc.com>
On Fri, Aug 25, 2023 at 10:00:01AM -0700 Guru Das Srinagesh wrote:
> On Aug 25 2023 13:44, Nicolas Schier wrote:
> > On Thu 24 Aug 2023 14:44:36 GMT, Guru Das Srinagesh wrote:
> > > > While testing, I thought that adding addresses without filtering-out duplicates
> > > > was odd; but as git-send-email does the unique filtering, it doesn't matter.
> > >
> > > Since I'm using `set()` in this script, the uniqueness is guaranteed here as
> > > well - there won't be any duplicates.
> >
> > I thought about patch files that already have 'To/Cc' headers (e.g.
> > 'git format-patch --to=... --cc=...' or by running add-maintainer.py
> > multiple times for updating the lists of recipients. The result is a
> > patch file with possible duplicated lines; but as written: it does
> > matter, effectively.
>
> Sorry, did you mean "does" or "does *not*"?
I'm sorry, "it doe not matter".
Nicolas
> I'll make sure to test v3 of this script out on patches that have To/Cc already
> included and also run it multiple times on the same patch (effectively the same
> thing).
>
> 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-27 5:55 UTC|newest]
Thread overview: 44+ 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 ` Guru Das Srinagesh
2023-08-03 8:23 ` [PATCH v2 1/1] scripts: Add add-maintainer.py Guru Das Srinagesh
2023-08-03 8:23 ` Guru Das Srinagesh
2023-08-03 9:04 ` Pavan Kondeti
2023-08-03 9:04 ` Pavan Kondeti
2023-08-10 18:52 ` Guru Das Srinagesh
2023-08-10 18:52 ` Guru Das Srinagesh
2023-08-23 15:14 ` Nicolas Schier
2023-08-23 15:14 ` Nicolas Schier
2023-08-24 21:44 ` Guru Das Srinagesh
2023-08-24 21:44 ` Guru Das Srinagesh
2023-08-25 11:44 ` Nicolas Schier
2023-08-25 11:44 ` Nicolas Schier
2023-08-25 17:00 ` Guru Das Srinagesh
2023-08-25 17:00 ` Guru Das Srinagesh
2023-08-27 5:52 ` Nicolas Schier [this message]
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-03 9:16 ` Neil Armstrong
2023-08-10 18:49 ` Guru Das Srinagesh
2023-08-10 18:49 ` Guru Das Srinagesh
2023-08-19 2:23 ` Guru Das Srinagesh
2023-08-19 2:23 ` Guru Das Srinagesh
2023-08-10 18:55 ` Guru Das Srinagesh
2023-08-10 18:55 ` Guru Das Srinagesh
2023-08-15 21:06 ` Krzysztof Kozlowski
2023-08-15 21:06 ` Krzysztof Kozlowski
2023-08-16 17:15 ` Guru Das Srinagesh
2023-08-16 17:15 ` Guru Das Srinagesh
2023-08-18 8:33 ` Neil Armstrong
2023-08-18 8:33 ` Neil Armstrong
2023-08-19 1:48 ` Guru Das Srinagesh
2023-08-19 1:48 ` Guru Das Srinagesh
2023-08-18 8:43 ` Krzysztof Kozlowski
2023-08-18 8:43 ` Krzysztof Kozlowski
2023-08-18 19:46 ` Bjorn Andersson
2023-08-18 19:46 ` Bjorn Andersson
2023-08-19 7:50 ` Krzysztof Kozlowski
2023-08-19 7:50 ` Krzysztof Kozlowski
2023-08-19 1:33 ` Guru Das Srinagesh
2023-08-19 1:33 ` Guru Das Srinagesh
2023-08-19 7:53 ` Krzysztof Kozlowski
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=ZOrktcX1L6WHmLBi@fjasle.eu \
--to=nicolas@fjasle.eu \
--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=quic_gurus@quicinc.com \
--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 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.