From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: tools@kernel.org
Subject: Re: b4 shazam not stripping ---
Date: Thu, 9 May 2024 11:05:01 -0400 [thread overview]
Message-ID: <20240509-elated-augmented-tench-5fbb9f@lemur> (raw)
In-Reply-To: <2510008e-23d5-4c15-a16c-be9de549a425@citrix.com>
On Thu, May 09, 2024 at 01:05:40AM GMT, Andrew Cooper wrote:
> Hello,
>
> b4 shazam 33b93fdf-bf16-49b8-aec2-0b2c19f5c471@suse.com
>
> is leaving the notes under --- in the commit message of the finalised patch.
>
> I cant spot anything obvious that should cause it to be mis-recognised,
> although it isn't a git-written diff. Reproduces with 0.13.y and
> master.
This should be now handled properly in master. Thank you for the report.
-K
next prev parent reply other threads:[~2024-05-09 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 0:05 b4 shazam not stripping --- Andrew Cooper
2024-05-09 13:40 ` Konstantin Ryabitsev
2024-05-09 13:43 ` Andrew Cooper
2024-05-09 13:47 ` Konstantin Ryabitsev
2024-05-09 13:48 ` Konstantin Ryabitsev
2024-05-09 13:50 ` Kernel.org Bugbot
2024-05-09 14:50 ` Kernel.org Bugbot
2024-05-09 15:05 ` Konstantin Ryabitsev [this message]
2024-05-09 15:09 ` Andrew Cooper
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=20240509-elated-augmented-tench-5fbb9f@lemur \
--to=konstantin@linuxfoundation.org \
--cc=andrew.cooper3@citrix.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).