public inbox for tools@linux.kernel.org
 help / color / mirror / Atom feed
* `b4` drops added trailers with peculiar patch
@ 2026-01-04 20:10 Miguel Ojeda
  2026-03-06  0:58 ` Konstantin Ryabitsev
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: Miguel Ojeda @ 2026-01-04 20:10 UTC (permalink / raw)
  To: Konstantin Ryabitsev; +Cc: tools

Hi Konstantin,

I just noticed that trying to use `shazam` on:

  https://lore.kernel.org/rust-for-linux/20251201165601.31484-1-atharvd440@gmail.com/

would not add the trailers, including Link, SoB, etc.

Poking around inside `b4`, I noticed that the patch has an space in
the `---` line.

The message is probably considered broken, but it means that
`get_body_parts()` will split unexpectedly and then the trailers will
be added after the `---` line.

So, later, when `b4` uses `git am` to apply, they get discarded
without warning :(

Would it make sense to try to notice potentially broken patches? I
know that kind of path is fraught with tears, but two ideas:

  - Double-check that the trailers are actually in the created commit,
and if not, sound the alarm, because something is not OK somewhere.

  - Perhaps a new case in that `if...elif...elif` with a pattern like
`^--- +\n`. Or perhaps even an `else` that warns if things look odd?

Thanks!

Cheers,
Miguel

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2026-03-06 19:45 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-01-04 20:10 `b4` drops added trailers with peculiar patch Miguel Ojeda
2026-03-06  0:58 ` Konstantin Ryabitsev
2026-03-06  1:15   ` Miguel Ojeda
2026-03-06  1:06 ` B4 Bugbot
2026-03-06 19:45 ` B4 Bugbot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox