public inbox for tools@linux.kernel.org
 help / color / mirror / Atom feed
* b4: feature request: send cover as separate e-mail even for a single patch
@ 2025-06-19  9:38 Luca Ceresoli
  2026-01-28 18:52 ` Breno Leitao
  0 siblings, 1 reply; 2+ messages in thread
From: Luca Ceresoli @ 2025-06-19  9:38 UTC (permalink / raw)
  To: tools; +Cc: Alexis Lothoré

Hello,

first and foremost: b4 is awesome, thank you!

A fixed behaviour of b4 is that when a series to be sent has only one
patch the cover letter is sent in the [PATCH 1/1] mail itself, under
the '---' separator, instead of a separate [PATCH 0/1] mail.

While I'm happy with this policy for simple self-standing patches that
do not need a cover, I find it annoying for other cases, such as:

 * a new iteration of a multi-patch series [0] where all patches except
   one have been applied (or dropped), so the series has become a
   one-patch: keeping the cover letter separate would make it
   consistent with the previous iterations

 * a single patch [1] that is not obvious, so a cover letter is used to
   provide the context, high-level view of a larger topic, etc

[0] https://lore.kernel.org/all/20250528-drm-bridge-convert-to-alloc-api-v4-1-f04e698c9a77@bootlin.com/
[1] https://lore.kernel.org/all/20250618-btf_skip_structs_on_stack-v1-1-e70be639cc53@bootlin.com/

I think both policies should be allowed, under user control. The user
interface to control it should include some of the following, in order
of necessity:

 * a command line flag for 'b4 send' to manually control which policy is
   desired each time a series is sent
 * a per-series parameter, saved within the JSON parameters in the
   cover letter commit, so the policy is consistent across iterations
 * a configuration parameter to set the default policy in lack of the
   two above

I tried some hacks in the b4 code to draft this feature but I just ended
up in breaking other things, so I reached out here for more informed
opinions.

Thanks for considering this addition to b4.

Best regards,
Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

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

* Re: b4: feature request: send cover as separate e-mail even for a single patch
  2025-06-19  9:38 b4: feature request: send cover as separate e-mail even for a single patch Luca Ceresoli
@ 2026-01-28 18:52 ` Breno Leitao
  0 siblings, 0 replies; 2+ messages in thread
From: Breno Leitao @ 2026-01-28 18:52 UTC (permalink / raw)
  To: Luca Ceresoli; +Cc: tools, Alexis Lothoré

Hello Luca, 

On Thu, Jun 19, 2025 at 11:38:55AM +0200, Luca Ceresoli wrote:
> Hello,
> 
> first and foremost: b4 is awesome, thank you!

Agreed! B4 is awesome.

> A fixed behaviour of b4 is that when a series to be sent has only one
> patch the cover letter is sent in the [PATCH 1/1] mail itself, under
> the '---' separator, instead of a separate [PATCH 0/1] mail.
> 
> While I'm happy with this policy for simple self-standing patches that
> do not need a cover, I find it annoying for other cases, such as:

Agree. I also have a similar requirement, to be able to send some very
specific and rare emails where I think a separate cover letter makes
more sense, other than the mixed-in case.

I've hacked a patch that I am using locally, simply passing
`--force-cover-letter` to `b4 send`, which will avoid the mixed-in
cover letter.

https://lore.kernel.org/all/20260127-force-cover-letter-v1-1-1ba8d7f9a64f@debian.org/

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

end of thread, other threads:[~2026-01-28 18:52 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-06-19  9:38 b4: feature request: send cover as separate e-mail even for a single patch Luca Ceresoli
2026-01-28 18:52 ` Breno Leitao

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