[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220930131430.djqv7brsxgkfoebx@meerkat.local>
Date: Fri, 30 Sep 2022 09:14:30 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Marijn Suijten <marijn.suijten@...ainline.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
linux-kernel@...r.kernel.org, tools@...ux.kernel.org
Subject: b4 prep range-diff (was Re: [PATCH v4 1/5] dt-bindings: mfd:
qcom-spmi-pmic: Add pm6125 compatible)
On Fri, Sep 30, 2022 at 02:31:18PM +0200, Marijn Suijten wrote:
> > FYI, it can do just that using "b4 trailers -uF [msgid]". See:
> > https://b4.docs.kernel.org/en/stable-0.10.y/contributor/trailers.html
>
> That's super cool and will save a lot of time. I'll also have to get
> accustomed to `b4 prep` and `b4 send`, though typically prefer to look
> at the `diff` between two `format-patch` revisions to make sure the
> changelog is complete and no erratic changes made it in.
(Dropping most people from CCs and adding the tools list.)
Hmm... Yes, we can do this, since we keep previously sent revisions tagged in
the tree. Something like:
b4 prep --compare v3
to show you a range-diff between v3 and the current revision.
-K
Powered by blists - more mailing lists