From: Rob Herring <robh@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: b4 v0.10.1 is available
Date: Tue, 4 Oct 2022 14:03:08 -0500 [thread overview]
Message-ID: <CAL_JsqJVY5Mk0e+wLXQBJnY0OwR=vh24MhqTqmaozBjaBAULKQ@mail.gmail.com> (raw)
In-Reply-To: <20220926172903.f3mudqmts5woudll@meerkat.local>
On Mon, Sep 26, 2022 at 12:29 PM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> Hello:
>
> B4 version 0.10.1 is now available. This release contains the following
> changes compared to 0.10.0 (among other minor improvements):
>
> - Fixes the crash with "b4 ty" when using a local binary to send mail, and
> generally improves the [sendemail] configuration section compatibility
> - The "send" and "prep" commands now properly include diffstats into generated
> patches
> - Does not force single-patch series to have a cover letter. The contents of
> the cover letter are now appended to the basement section of the patch.
> - Does not force "v1" to be added to the prefixes
>
> For upgrading instructions, please see docs:
> https://b4.docs.kernel.org/en/stable-0.10.y/installing.html
>
> Special thanks to the following people for the testing and bugreports:
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.
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.
Rob
next prev parent reply other threads:[~2022-10-04 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 17:29 b4 v0.10.1 is available Konstantin Ryabitsev
2022-10-04 19:03 ` Rob Herring [this message]
2022-10-07 18:11 ` Konstantin Ryabitsev
2022-10-27 19:38 ` Konstantin Ryabitsev
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='CAL_JsqJVY5Mk0e+wLXQBJnY0OwR=vh24MhqTqmaozBjaBAULKQ@mail.gmail.com' \
--to=robh@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.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.