Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
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: Sun, 14 Jun 2026 15:21:14 -0300	[thread overview]
Message-ID: <e3b32690-651a-4224-87f3-ba78757ccac2@gmail.com> (raw)
In-Reply-To: <20260614-unbiased-favorite-marmoset-194aff@lemur>


[-- Attachment #1.1: Type: text/plain, Size: 1231 bytes --]

On 6/14/26 12:40, Konstantin Ryabitsev wrote:
> On Sat, Jun 13, 2026 at 02:30:03AM -0300, Cássio Gabriel wrote:

>> ---
>> base-commit: 474350a3035537184556061872e9e905b47774ca
> 
> This is unrelated to the patch, but I did notice that something went strangely
> wrong with this submission. The base-commit line moved up above the basement
> into the header, and the bottom is truncated:
> 
> https://lore.kernel.org/tools/20260613-resend-signature-fix-v2-1-ddd560f810bc@gmail.com/T/#u
> 
> 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}

And this happens when I send a patch series using
this custom prep-cover + ${signature}[1] --> https://lore.kernel.org/all/20260608-asoc-of-node-scoped-cleanup-v1-0-9e3ac518dc2e@gmail.com

And without ${signature} --> https://lore.kernel.org/all/20260612-alsa-cea-channel-allocation-v1-0-b1bcbb6b1051@gmail.com


Note: I took off the signature 'cause I wanted to.I took off the signature 'cause I wanted to.

-- 
Thanks,
Cássio


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2026-06-14 18:21 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 [this message]
2026-06-15 18:19     ` Konstantin Ryabitsev
2026-06-16  2:28       ` Cássio Gabriel

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=e3b32690-651a-4224-87f3-ba78757ccac2@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