From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: me@black-desk.cn, git@vger.kernel.org
Subject: Re: [PATCH] b4: include change-id in cover template
Date: Fri, 10 Jul 2026 10:02:29 -0700 [thread overview]
Message-ID: <xmqqik6mdbh6.fsf@gitster.g> (raw)
In-Reply-To: <alCxgqybWb9eDEG0@pks.im> (Patrick Steinhardt's message of "Fri, 10 Jul 2026 10:46:58 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> On Fri, Jul 10, 2026 at 03:22:13PM +0800, Chen Linxuan via B4 Relay wrote:
>> From: Chen Linxuan <me@black-desk.cn>
>>
>> With b4 0.15.2, I hit a local failure after sending a series with the
>> in-tree cover template. The generated sent/<change-id>-vN tag contained
>> base-commit, but did not contain change-id, and later b4 commands failed
>> when trying to read it:
>>
>> CRITICAL: Tag sent/... does not contain change-id info
>>
>> Looking at b4's source, the sent tag message is derived from the rendered
>> cover letter. The same code later parses that tag and expects both
>> base-commit and change-id to be present. The default b4 cover template
>> has both trailers, but our in-tree template only has base-commit.
>>
>> Add the missing change-id trailer next to base-commit so sent tags
>> produced from the project template remain readable by b4's reroll and
>> comparison logic.
>
> Ah, that's indeed an oversight on my side. So this change looks good to
> me, thanks!
>
> Patrick
I would have slightly preferred to see the observation part fully in
present tense (instead of "I did and it failed"), perhaps like so:
When sending a series with the in-tree cover template, the
generated sent/<change-id>-vN tag contains base-commit but lacks
change-id. Later b4 commands fail when trying to read it.
but that is a minor point.
Will queue. Thanks, both.
prev parent reply other threads:[~2026-07-10 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 7:22 [PATCH] b4: include change-id in cover template Chen Linxuan via B4 Relay
2026-07-10 8:46 ` Patrick Steinhardt
2026-07-10 17:02 ` Junio C Hamano [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=xmqqik6mdbh6.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@black-desk.cn \
--cc=ps@pks.im \
/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