From: "Morten Brørup" <mb@smartsharesystems.com>
To: <bruce.richardson@intel.com>, <david.marchand@redhat.com>
Cc: <konstantin.ananyev@huawei.com>, <thomas@monjalon.net>, <dev@dpdk.org>
Subject: mailmap causing checkpatch warnings
Date: Sat, 24 Dec 2022 12:05:50 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D875E7@smartserver.smartshare.dk> (raw)
Bruce, David,
I just submitted a patch with an Acked-by from Konstantin, using his current (Huawei) email address, and it triggered the following checkpatch warning:
Konstantin Ananyev mail differs from primary mail, please fix the commit message or update .mailmap.
Some people have more than one active email address, so this checkpatch behavior is wrong.
Med venlig hilsen / Kind regards,
-Morten Brørup
next reply other threads:[~2022-12-24 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 11:05 Morten Brørup [this message]
2022-12-27 10:15 ` Thomas Monjalon
2022-12-27 11:15 ` Morten Brørup
2023-01-04 11:45 ` Konstantin Ananyev
2023-01-05 8:46 ` Thomas Monjalon
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=98CBD80474FA8B44BF855DF32C47DC35D875E7@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=thomas@monjalon.net \
/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 NNTP newsgroup(s).