From: Bruce Richardson <bruce.richardson@intel.com>
To: "Varghese, Vipin" <Vipin.Varghese@amd.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH 2/2] mailmap: sort mailmap
Date: Wed, 15 Oct 2025 08:41:10 +0100 [thread overview]
Message-ID: <aO9QFopivyfSCal_@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <PH7PR12MB8596E4E3C090C148BA8A528582E8A@PH7PR12MB8596.namprd12.prod.outlook.com>
On Wed, Oct 15, 2025 at 07:38:32AM +0000, Varghese, Vipin wrote:
> [Public]
>
> +1 for the change
>
> > +Vipin Padmam Ramesh <vipinp@vmware.com>
> > Vipin Varghese <vipin.varghese@amd.com> <vipin.varghese@intel.com>
>
> Should we update, ` Vipin Varghese <vipin.varghese@amd.com> <vipin.varghese@intel.com>` to ` Vipin Varghese <vipin.varghese@amd.com>`
>
I don't think so. That would result in all your commits made under the old
email address being counted as written by a different person. The map entry
is to map the old email address to the new one.
/Bruce
next prev parent reply other threads:[~2025-10-15 7:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 14:27 [PATCH 0/2] Improve mailmap file Bruce Richardson
2025-08-08 14:27 ` [PATCH 1/2] devtools/mailmap_ctl: script to work with mailmap Bruce Richardson
2025-08-08 16:44 ` Marat Khalili
2025-08-08 16:47 ` Bruce Richardson
2025-08-08 19:58 ` Bruce Richardson
2025-08-11 11:27 ` Marat Khalili
2025-08-08 14:27 ` [PATCH 2/2] mailmap: sort mailmap Bruce Richardson
2025-10-15 7:38 ` Varghese, Vipin
2025-10-15 7:41 ` Bruce Richardson [this message]
2025-08-08 21:08 ` [PATCH v2 0/2] Improve mailmap file Bruce Richardson
2025-08-08 21:08 ` [PATCH v2 1/2] devtools/mailmap_ctl: script to work with mailmap Bruce Richardson
2025-08-11 11:28 ` Marat Khalili
2025-10-15 14:20 ` Robin Jarry
2025-08-08 21:08 ` [PATCH v2 2/2] mailmap: sort mailmap Bruce Richardson
2025-08-11 12:18 ` Marat Khalili
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=aO9QFopivyfSCal_@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=Vipin.Varghese@amd.com \
--cc=dev@dpdk.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 NNTP newsgroup(s).