Re: b4 v0.10.1 is available

[Konstantin Ryabitsev <konstantin@linuxfoundation.org>]

On Tue, Oct 04, 2022 at 02:03:08PM -0500, Rob Herring wrote:
> I found a couple of issues with trailers and send. I'm on the current master.
> 
> In 'b4 trailers', if the patch id doesn't match exactly and it finds
> some trailers, b4 just prints 'No trailer updates found.' which is
> misleading. Can it have a fallback to subject matching or at least
> print when there isn't an exact match and list the trailers found.

Strange, I thought we already did fall back to subject matching when we
couldn't match by patch-id. I'll work to set up a couple of testcases so we
can easily identify such regressions (if that's what it is) in the future.

> It's quite common to either have minor changes (and a judgement call
> on whether tags still apply) or a review that's 'With X fixed,
> Reviewed-by: ...".
> 
> The 2nd issue is with 'b4 send' and seems to have been introduced
> recently. I have a commit msg like this:
> "
> Some commit
> 
> Signed-off-by: ...
> ---
>  v2: https://lore.kernel.org/all/20220909204509.2169512-1-robh@kernel.org/
>    - Rework YACC code to handle configN formats in C code
>    - Add a warning when an unknown configN attr is found
> "
> 
> I'm putting '---' in the commit to store the changes for the commit.
> The patch ends up with 2 '---' lines, but git drops everything after
> the first one. The issue is that
> '//lore.kernel.org/all/20220909204509.2169512-1-robh@kernel.org/' is
> added to the Cc list.

Thank you for the report -- I wasn't expecting to find changelog entries in
the commits, so I'll add that to tests as well and fix it up.

-K