From: Breno Leitao <leitao@debian.org>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: "Kernel.org Tools" <tools@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
kernel-team@meta.com
Subject: Re: [PATCH b4] send: Add --force-cover-letter to send separate cover for single patch patch series
Date: Wed, 28 Jan 2026 10:47:32 -0800 [thread overview]
Message-ID: <aXpZpEayZstZYmRh@gmail.com> (raw)
In-Reply-To: <DG0FDQ2I7T4R.Z5XKN00DAQ42@bootlin.com>
On Wed, Jan 28, 2026 at 07:14:37PM +0100, Luca Ceresoli wrote:
> Hello Breno,
>
> On Tue Jan 27, 2026 at 1:53 PM CET, Breno Leitao wrote:
> > By default, b4 mixes the cover letter content into the patch body
> > (under the --- cut line) when sending a single-patch series. Add
> > --force-cover-letter option to allow sending a separate cover letter
> > message (as 0/1) even for single-patch series.
> >
> > This is useful when developers want to send a long cover letter with
> > extra information about an issue, and a commit. Having the cover-letter
> > "mixed-in" makes it hard to follow.
> >
> > Example:
> > * https://lore.kernel.org/all/20260127-ipmi-v1-0-ba5cc90f516f@debian.org/
> >
> > Signed-off-by: Breno Leitao <leitao@debian.org>
>
> Thanks! This is a feature I had requiested some time ago [0] so I'm very
> heppy to see it implemented.
>
> I just tested it successfully to send a 1-patch series [1].
>
> Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Awesome. I was missing it also, and I haven't seen your request.
Thanks for the tested!
--breno
next prev parent reply other threads:[~2026-01-28 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 12:53 [PATCH b4] send: Add --force-cover-letter to send separate cover for single patch patch series Breno Leitao
2026-01-28 18:14 ` Luca Ceresoli
2026-01-28 18:47 ` Breno Leitao [this message]
2026-01-29 11:18 ` Antonin Godard
2026-01-29 13:21 ` Breno Leitao
2026-01-29 13:51 ` Antonin Godard
2026-01-29 14:03 ` Breno Leitao
2026-01-29 14:15 ` Mark Brown
2026-01-29 15:00 ` Breno Leitao
2026-02-24 18:57 ` 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=aXpZpEayZstZYmRh@gmail.com \
--to=leitao@debian.org \
--cc=kernel-team@meta.com \
--cc=konstantin@linuxfoundation.org \
--cc=luca.ceresoli@bootlin.com \
--cc=tools@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.