From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: "Kernel.org Tools" <tools@linux.kernel.org>
Subject: Re: Regression in b4 send since 0.11.0 when commit title length >=55 <=62
Date: Tue, 3 Jan 2023 17:52:16 -0500 [thread overview]
Message-ID: <20230103225216.lb5kxeesqehegazz@meerkat.local> (raw)
In-Reply-To: <b79c49b3-5815-7100-e99c-440e1840b3f9@theobroma-systems.com>
On Tue, Jan 03, 2023 at 01:25:00PM +0100, Quentin Schulz wrote:
> Hi,
>
> I've recently updated from 0.10.x to 0.11.1 and have an issue with b4 send.
>
> When a commit has a title of length comprised between 55 and 62 characters,
> the Subject header content in the eml file starts on the next line and makes
> git-send-email unhappy.
Thank you for the report. To be pedantic, this is a bug in git-send-email, but
I also find the fact that Python does that really annoying.
The latest commit in master and stable-0.11.y should restore the previous
behaviour.
-K
prev parent reply other threads:[~2023-01-03 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 12:25 Regression in b4 send since 0.11.0 when commit title length >=55 <=62 Quentin Schulz
2023-01-03 22:52 ` 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=20230103225216.lb5kxeesqehegazz@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=quentin.schulz@theobroma-systems.com \
--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).