From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Jochen Behrens <jochen.behrens@broadcom.com>, dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v3] mailmap: clean up vmware entries
Date: Thu, 18 Apr 2024 11:46:46 +0100 [thread overview]
Message-ID: <c7d84c91-eeeb-46fc-8830-a79249be0f3f@amd.com> (raw)
In-Reply-To: <20240417161901.1919433-1-jochen.behrens@broadcom.com>
On 4/17/2024 5:19 PM, Jochen Behrens wrote:
> VMware was acquired by Broadcom, and vmware e-mail addresses will
> be invalid in the future.
>
> Add broadcom.com addresses for those still in the company.
> Place broadcom.com addresses first, as they are now the active ones.
> Retain the old addresses from git history behind them.
>
> Signed-off-by: Jochen Behrens <jochen.behrens@broadcom.com>
>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
prev parent reply other threads:[~2024-04-18 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 23:39 [PATCH] mailmap: clean up vmware entries Jochen Behrens
2024-04-16 7:20 ` Thomas Monjalon
2024-04-17 0:06 ` [PATCH v2] " Jochen Behrens
2024-04-17 16:19 ` [PATCH v3] " Jochen Behrens
2024-04-18 10:46 ` Ferruh Yigit [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=c7d84c91-eeeb-46fc-8830-a79249be0f3f@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=jochen.behrens@broadcom.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 read-only IMAP folder(s) and NNTP newsgroup(s).