DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH] mailmap: add a mailmap file to DPDK
Date: Tue, 20 Oct 2020 14:07:22 +0100	[thread overview]
Message-ID: <20201020130722.304989-1-bruce.richardson@intel.com> (raw)

Since a number of contributors to DPDK have submitted patches to DPDK under
more than one email address, we should maintain a mailmap file to properly
track their commits using "shortlog". It also helps fix up any mangled
names, for example, with surname/firstname reversed, or with incorrect
capitalization.

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---

while this list is almost certainly incomplete, this should serve as a
reasonable start-point for building a more complete one.
---
 .mailmap | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 .mailmap

diff --git a/.mailmap b/.mailmap
new file mode 100644
index 000000000..720107c7b
--- /dev/null
+++ b/.mailmap
@@ -0,0 +1,15 @@
+Anatoly Burakov <anatoly.burakov@intel.com>
+Bruce Richardson <bruce.richardson@intel.com>
+Chas Williams <chas3@att.com> <ciwillia@brocade.com> <3chas3@gmail.com>
+David Marchand <david.marchand@redhat.com> <david.marchand@6wind.com>
+Harish Patil <harish.patil@cavium.com> <harish.patil@qlogic.com>
+Hemant Agrawal <hemant.agrawal@nxp.com> <Hemant@freescale.com>
+Jerin Jacob <jerinj@marvell.com> <jerin.jacob@caviumnetworks.com>
+Jingjing Wu <jingjing.wu@intel.com>
+Luca Boccassi <bluca@debian.org> <luca.boccassi@gmail.com> <lboccass@brocade.com>
+Ori Kam <orika@nvidia.com> <orika@mellanox.com>
+Pablo De Lara <pablo.de.lara.guarch@intel.com>
+Rahul Shah <rahul.r.shah@intel.com>
+Stephen Hemminger <stephen@networkplumber.org> <shemming@brocade.com> <sthemmin@microsoft.com>
+Thomas Monjalon <thomas@monjalon.net> <thomas.monjalon@6wind.com>
+Yuanhan Liu <yliu@fridaylinux.org> <yuanhan.liu@linux.intel.com>
-- 
2.25.1


             reply	other threads:[~2020-10-20 13:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20 13:07 Bruce Richardson [this message]
2020-10-20 13:22 ` David Marchand
2020-10-20 14:29 ` Thomas Monjalon
2020-10-20 15:03   ` Bruce Richardson
2020-10-20 15:17     ` Thomas Monjalon
2020-10-20 15:32       ` Bruce Richardson
2020-10-20 15:38         ` Thomas Monjalon
2020-10-20 15:44           ` Bruce Richardson
2020-10-21 16:55 ` [dpdk-dev] [PATCH v2] " Bruce Richardson
2022-11-04 12:13 ` [PATCH v3] mailmap: add " Bruce Richardson
2022-11-04 12:16   ` Bruce Richardson
2022-11-24 12:13 ` [PATCH v4] " David Marchand
2022-11-24 13:43   ` Bruce Richardson
2022-11-24 13:49     ` David Marchand
2022-11-24 13:57       ` Thomas Monjalon
2022-11-24 15:08         ` Bruce Richardson
2022-11-24 17:21           ` Thomas Monjalon
2022-11-24 16:51     ` Stephen Hemminger
2022-11-24 17:19       ` Thomas Monjalon
2022-11-28 17:18         ` Tyler Retzlaff
2022-11-24 15:44 ` [PATCH v5] " David Marchand
2022-11-24 17:21   ` Ferruh Yigit
2022-11-24 17:26     ` Thomas Monjalon
2022-11-24 17:34       ` Ferruh Yigit
2022-11-24 19:42         ` Thomas Monjalon
2022-11-25 14:54 ` [PATCH v6] " David Marchand
2022-11-25 16:08   ` Dumitrescu, Cristian
2022-11-27 10:27     ` 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=20201020130722.304989-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.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).