From: Thomas Monjalon <thomas@monjalon.net>
To: "Morten Brørup" <mb@smartsharesystems.com>,
"Konstantin Ananyev" <konstantin.ananyev@huawei.com>
Cc: "bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: mailmap causing checkpatch warnings
Date: Thu, 05 Jan 2023 09:46:40 +0100 [thread overview]
Message-ID: <8162093.T7Z3S40VBb@thomas> (raw)
In-Reply-To: <480af268a3104f5e93729d0e0182c9a5@huawei.com>
04/01/2023 12:45, Konstantin Ananyev:
>
> >
> > 24/12/2022 12:05, Morten Brørup:
> > > 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.
> >
> > Do you know how to accept all emails of .mailmap?
> >
> > > Some people have more than one active email address, so this checkpatch behavior is wrong.
> >
> > Konstantin, what is your main email address?
>
>
> I use both, but if that's a problem for one of our tools,
> I can stick with ACK-ing all patches using just one of them.
> Would that help?
Yes it would help in this case, but perhaps the tool should be fixed.
prev parent reply other threads:[~2023-01-05 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 11:05 mailmap causing checkpatch warnings Morten Brørup
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 [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=8162093.T7Z3S40VBb@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=mb@smartsharesystems.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.