From: "Cássio Gabriel" <cassiogabrielcontato@gmail.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "Kernel.org Tools" <tools@kernel.org>
Subject: Re: [PATCH b4 v2] ez: avoid duplicate signatures on resend
Date: Mon, 15 Jun 2026 23:28:10 -0300 [thread overview]
Message-ID: <7fc9d7e7-d6ce-449d-a511-8754480f3c5b@gmail.com> (raw)
In-Reply-To: <20260615-beaver-of-unknown-revolution-ec6da5@meerkat>
[-- Attachment #1.1: Type: text/plain, Size: 1051 bytes --]
On 6/15/26 15:19, Konstantin Ryabitsev wrote:
> On Sun, Jun 14, 2026 at 03:21:14PM -0300, Cássio Gabriel wrote:
>>> I've never seen this happen, so I'd like to understand what may have caused
>>> this.
>>
>> This happens when I send a single patch using
>> my custom 'b4.prep-cover-template':
>>
>> ${cover}
>> ---
>> ${shortlog}
>>
>> ${diffstat}
>> ---
>> base-commit: ${base_commit}
>> ${prerequisites}
>
> This did unearth a bug in how we were looking for basement info. Your custom
> cover template no longer includes "change-id", which is what we were looking
> for to identify the "---" separated sections.
Yes, and at first glance I did not pay much attention to that bug to be honest
since was I just testing my custom settings.
> I am putting a fix in to use more than just "change-id" but I'm curious -- did
> you omit it on purpose, or is it just an oversight?
Yes, I omit it on purpose just to see how it would come out - and that is the result.
Interesting bug!
--
Thanks,
Cássio
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2026-06-16 2:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-13 5:30 [PATCH b4 v2] ez: avoid duplicate signatures on resend Cássio Gabriel
2026-06-14 15:40 ` Konstantin Ryabitsev
2026-06-14 18:21 ` Cássio Gabriel
2026-06-15 18:19 ` Konstantin Ryabitsev
2026-06-16 2:28 ` Cássio Gabriel [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=7fc9d7e7-d6ce-449d-a511-8754480f3c5b@gmail.com \
--to=cassiogabrielcontato@gmail.com \
--cc=konstantin@linuxfoundation.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