From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: b4 send needs a subject in the cover
Date: Fri, 9 Dec 2022 16:05:57 -0500 [thread overview]
Message-ID: <20221209210557.dii35qbb3iltxsgd@meerkat.local> (raw)
In-Reply-To: <Y5EyJaSdOXL3Nzwg@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On Thu, Dec 08, 2022 at 12:39:01AM +0000, Mark Brown wrote:
> On Wed, Dec 07, 2022 at 11:02:41PM +0000, Mark Brown wrote:
> > If I've got a patch series with a single patch in it then there's no
> > need for a cover letter and if it's the first version no need for a
> > changelog so I'd expect to just delete all the text in the b4 cover
> > other than the recipients. However if I do that then what seems to end
> > up happening is that the first recipient gets deleted, I'm guessing
> > parsed as a subject which then doesn't get used due to this being a
> > single message.
> >
> > I can see why this happens but it's a bit of a gotcha - printing the
> > subject might help make it clearer what's going on in this case?
>
> ...and further if you look at
>
> https://lore.kernel.org/r/20221207-arm64-mvfr-fix-v1-0-0c739eb77bea@kernel.org
>
> you'll see that the to and Cc lines end up in the sent patch which isn't
> entirely what would be expected.
I believe the latest master should fix both of these problems.
-K
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2022-12-09 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 23:02 b4 send needs a subject in the cover Mark Brown
2022-12-08 0:39 ` Mark Brown
2022-12-09 21:05 ` Konstantin Ryabitsev [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=20221209210557.dii35qbb3iltxsgd@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=broonie@kernel.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 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.