[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6f475c9b-dc0e-078e-9aa2-d876a1e02467@linaro.org>
Date: Sat, 19 Aug 2023 09:50:56 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Bjorn Andersson <quic_bjorande@...cinc.com>
Cc: Guru Das Srinagesh <quic_gurus@...cinc.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Nicolas Schier <nicolas@...sle.eu>,
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, u.kleine-koenig@...gutronix.de,
linux-kernel@...r.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 v2 0/1] Add add-maintainer.py script
On 18/08/2023 21:46, Bjorn Andersson wrote:
>>>
>>> With this script, the workflow would be as simple as:
>>>
>>> 1. Generate patches using `git format-patch`
>>> 2. Run `add-maintainer.py` on the above patches
>>> 3. `git send-email` the patches.
>>
>> So one more unnecessary step (2). I don't think it is easier than my
>> workflow.
>>
>> I just do only 1 and 3 and that's it. The simplest way ever.
>>
>
> There's no get_maintainer.pl in either 1, or 3, so obviously this isn't
> the only thing you do.
>
> Thanks for the link to your alias below, it's now clear that you don't
> need an extra step in the procedure, if you only have your extra wrapper
> around step 3.
>
>
> I now also understand why you never ever have a cover-letter, something
> Guru's proposed flow handles quite nicely.
It's not related. I usually don't create cover letter from laziness, but
pretty often I create them as well and my script/alias works there
perfectly. Cover letter is just one more step:
1. git branch --edit-description
2. git format-patch --cover-letter (with format.coverFromDescription =
subject in gitconfig)
3. git_send_email 0*
No need to run any other tool, no need to add any maintainer entries
(unless touching defconfig and specific soc@ stuff, but this is always
the case regardless of tools).
Really, that script proposed here is the unnecessary step.
Rob's approach with git send-email identity required some work for
cover-letter, but it was also running get_maintainer.pl per each patch,
so recipients did not receive everything. Unless patchset is big, I
prefer to send everything to everyone.
>
>
> That said, b4 prep and b4 send seems like a better suggestion to those
> who doesn't already have a workflow in place.
Yes.
Best regards,
Krzysztof
Powered by blists - more mailing lists