From: Guru Das Srinagesh <quic_gurus@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: 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>,
"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 0/1] Add add-maintainer.py script
Date: Fri, 18 Aug 2023 18:33:04 -0700 [thread overview]
Message-ID: <20230819013303.GA22393@quicinc.com> (raw)
In-Reply-To: <6fb1176f-90f1-7a65-3ab5-f6447418c51e@linaro.org>
On Aug 18 2023 10:43, Krzysztof Kozlowski wrote:
> >> For newcomers, OTOH, I would either recommend simple workflow or just
> >> use b4. Why? Because if you cannot use git-send-email, then it means
> >> your email setup will make your life difficult and adding maintainers to
> >> existing patch won't help you.
> >
> > You've mentioned a "simple workflow" many times - could you please share more
> > details on the steps you follow in your workflow for sending patches?
>
> I shared it on LKML few times already (and Rob's git send-email identity
> is also on LKML), so one more time:
>
> https://github.com/krzk/tools/blob/master/linux/.bash_aliases_linux#L91
Thank you for sharing this - it is really neat indeed and you certainly don't
need a step #2 with this method.
However, I see areas for improvement in the alias:
- Subsystem-specific mailing lists, maintainers, reviewers, and other roles are
all marked as "To: " sans distinction via the alias whereas
`add-maintainer.py` and `b4` both provide marking of lists as "Cc: " which
seems aesthetically and semantically more pleasing.
- Only `add-maintainer.py` allows for maintainers to be selectively in "To: "
and "Cc: " for patches in a series depending on whether they are the
maintainers for that particular patch or not.
> >> This tool depends on the command line and shell interface of
> >> scripts/get_maintainers.pl which is another reason why it might not be a
> >> good idea.
> >
> > Could you please elaborate on why depending on the output of
> > `get_maintainer.pl` is a bad idea? It's what everyone uses, no?
>
> No, because if interface changes you need to update two tools.
But `b4 prep --auto-to-cc` also uses `get_maintainer.pl`!
Also, in your previous email you said to "just use b4", which also depends on
the command line and shell interface of `get_maintainers.pl`. Depending on
`get_maintainer.pl` is therefore perfectly okay - there is no need to reinvent
it or disregard it for whatever reasons.
Thank you.
Guru Das.
WARNING: multiple messages have this Message-ID (diff)
From: Guru Das Srinagesh <quic_gurus@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: 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>,
"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 0/1] Add add-maintainer.py script
Date: Fri, 18 Aug 2023 18:33:04 -0700 [thread overview]
Message-ID: <20230819013303.GA22393@quicinc.com> (raw)
In-Reply-To: <6fb1176f-90f1-7a65-3ab5-f6447418c51e@linaro.org>
On Aug 18 2023 10:43, Krzysztof Kozlowski wrote:
> >> For newcomers, OTOH, I would either recommend simple workflow or just
> >> use b4. Why? Because if you cannot use git-send-email, then it means
> >> your email setup will make your life difficult and adding maintainers to
> >> existing patch won't help you.
> >
> > You've mentioned a "simple workflow" many times - could you please share more
> > details on the steps you follow in your workflow for sending patches?
>
> I shared it on LKML few times already (and Rob's git send-email identity
> is also on LKML), so one more time:
>
> https://github.com/krzk/tools/blob/master/linux/.bash_aliases_linux#L91
Thank you for sharing this - it is really neat indeed and you certainly don't
need a step #2 with this method.
However, I see areas for improvement in the alias:
- Subsystem-specific mailing lists, maintainers, reviewers, and other roles are
all marked as "To: " sans distinction via the alias whereas
`add-maintainer.py` and `b4` both provide marking of lists as "Cc: " which
seems aesthetically and semantically more pleasing.
- Only `add-maintainer.py` allows for maintainers to be selectively in "To: "
and "Cc: " for patches in a series depending on whether they are the
maintainers for that particular patch or not.
> >> This tool depends on the command line and shell interface of
> >> scripts/get_maintainers.pl which is another reason why it might not be a
> >> good idea.
> >
> > Could you please elaborate on why depending on the output of
> > `get_maintainer.pl` is a bad idea? It's what everyone uses, no?
>
> No, because if interface changes you need to update two tools.
But `b4 prep --auto-to-cc` also uses `get_maintainer.pl`!
Also, in your previous email you said to "just use b4", which also depends on
the command line and shell interface of `get_maintainers.pl`. Depending on
`get_maintainer.pl` is therefore perfectly okay - there is no need to reinvent
it or disregard it for whatever reasons.
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-19 1:34 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
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 [this message]
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=20230819013303.GA22393@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=krzysztof.kozlowski@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 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.