From: Ricardo Ribalda <ribalda@chromium.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, Mark Brown <broonie@kernel.org>
Subject: Re: b4 prep/send: single patch mode
Date: Thu, 24 Nov 2022 21:30:03 +0100 [thread overview]
Message-ID: <CANiDSCtZhcBw60gBLjxzoObCjt0V--Vx17roCRC1G=Nb+ttzyw@mail.gmail.com> (raw)
In-Reply-To: <20221124202437.td63ug6zmbeka4xj@meerkat.local>
Awesome, thanks!
Sorry for the noise :)
On Thu, 24 Nov 2022 at 21:24, Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> On Thu, Nov 24, 2022 at 06:49:34PM +0100, Ricardo Ribalda wrote:
> > Hi
> >
> > I have moved all my developer workflow to b4 and I am super happy,
> > thanks for that :)
>
> Excellent!
>
> > There is one caveat though ;):
> >
> > When I have to send a patchset with only one patch it seems redundant
> > to send a cover letter, Most of the time, it is a copy of the commit
> > message at 1/1 plus a link to the previous version of the patch in
> > lore.
> >
> > Would it make sense to add that info after the --- and do not send the
> > cover-letter if there is only one patch on the set?
>
> This has been possible since commit 6c215d83473d732cf1208c17a00a8ebc7d7526eb
> -- you should update to the latest master (or at least to the latest
> stable-0.10.y).
>
> -K
--
Ricardo Ribalda
prev parent reply other threads:[~2022-11-24 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 17:49 b4 prep/send: single patch mode Ricardo Ribalda
2022-11-24 20:24 ` Konstantin Ryabitsev
2022-11-24 20:30 ` Ricardo Ribalda [this message]
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='CANiDSCtZhcBw60gBLjxzoObCjt0V--Vx17roCRC1G=Nb+ttzyw@mail.gmail.com' \
--to=ribalda@chromium.org \
--cc=broonie@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).