From: Maxime Ripard <maxime@cerno.tech>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: b4 bugs / future improvements
Date: Tue, 29 Nov 2022 21:52:55 +0100 [thread overview]
Message-ID: <20221129205255.pfpuafph6mi2x57o@houat> (raw)
In-Reply-To: <20221129171453.f74wxgd3kemsvy6q@meerkat.local>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
On Tue, Nov 29, 2022 at 12:14:53PM -0500, Konstantin Ryabitsev wrote:
> On Wed, Nov 09, 2022 at 03:14:59PM +0100, Maxime Ripard wrote:
> > > It seems to be related to
> > > https://github.com/marlam/msmtp-mirror/issues/51 except I don't have
> > > set_from_header in my config. I've tried to use allow_from_override and
> > > force it to off, and it didn't help.
> >
> > I just discovered something else.
> >
> > For various reasons, on one of my series I keep a per-commit changelog,
> > in the commit log after a ---
> >
> > This works generally fine, until I run b4 trailers -u which seems to
> > drop the entire content after --- when adding the tags.
>
> This took a while to track and fix, but this should no longer happen in master
> and stable-0.10.y. Thank you for the report.
Awesome, I'll give it a try, thanks a lot
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-11-29 20:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 15:36 b4 bugs / future improvements Maxime Ripard
2022-10-18 20:18 ` Konstantin Ryabitsev
2022-10-18 20:29 ` Mark Brown
2022-10-18 20:37 ` Konstantin Ryabitsev
2022-10-19 8:04 ` Maxime Ripard
2022-10-19 19:16 ` Konstantin Ryabitsev
2022-10-20 8:41 ` Maxime Ripard
2022-10-19 2:05 ` Rob Herring
2022-10-19 8:01 ` Maxime Ripard
2022-10-19 19:21 ` Konstantin Ryabitsev
2022-10-20 8:49 ` Maxime Ripard
2022-11-09 14:14 ` Maxime Ripard
2022-11-29 17:14 ` Konstantin Ryabitsev
2022-11-29 20:52 ` Maxime Ripard [this message]
2023-05-05 7:17 ` Maxime Ripard
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=20221129205255.pfpuafph6mi2x57o@houat \
--to=maxime@cerno.tech \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox