From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Breno Leitao" <leitao@debian.org>
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: Thu, 29 Jan 2026 14:51:05 +0100 [thread overview]
Message-ID: <DG14EHTYTJTN.2NQI0XSURUJIP@bootlin.com> (raw)
In-Reply-To: <aXteOVMUIKNzv2te@gmail.com>
On Thu Jan 29, 2026 at 2:21 PM CET, Breno Leitao wrote:
[...]
>> I do find myself needing the last use-case sometimes, when the series does
>> not require a cover-letter.
>
> Why do you need this case? I undertand a cover letter is required for
> a multi patch series, so, it can have an easy merge commit when merging
> the series.
Some project ignore merge commits altogether, so I regularly see series without
cover letters. Are merge commits that frequent? I'm not judging on whether it's
good practice or not, but introducing a --force-cover-letter option would maybe
not leave room for having such a use-case in the future.
Antonin
next prev parent reply other threads:[~2026-01-29 13:51 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
2026-01-29 11:18 ` Antonin Godard
2026-01-29 13:21 ` Breno Leitao
2026-01-29 13:51 ` Antonin Godard [this message]
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=DG14EHTYTJTN.2NQI0XSURUJIP@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=kernel-team@meta.com \
--cc=konstantin@linuxfoundation.org \
--cc=leitao@debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox