All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: <dev@dpdk.org>, <david.marchand@redhat.com>, <thomas@monjalon.net>
Subject: Re: [PATCH v3] mailmap: add file to DPDK
Date: Fri, 4 Nov 2022 12:16:28 +0000	[thread overview]
Message-ID: <Y2UCnGtbUxRoSBqN@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20221104121334.15177-1-bruce.richardson@intel.com>

On Fri, Nov 04, 2022 at 12:13:34PM +0000, Bruce Richardson wrote:
> 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. By keeping this file in the DPDK repository,
> rather than committers maintaining their own copies, it allows
> individual contributors to edit it to update their own email address
> preferences if so desired.
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> 
> ---
> 
> V3: Updated version of file
> 
> V2: Massively expanded list by running a script on the repo to pick out
> names associated with multiple emails. Within each line, the emails are
> listed in inverse chronological order of use, based on assumption that last
> email used is the most up-to-date and the one that is desired to be used in
> shortlog.
> ---

Thoma, David, I realise you both maintain a "master" copy of email
addresses for DPDK contributors, so feel free to submit a v4 with that
list. Overall, though, I really think we need to have a mailmap file in the
repo, rather than asking people to maintain their own if they want
repository stats. In the meantime, I am submitting this v3 in the hope
others find it useful.

Thanks,
/Bruce

  reply	other threads:[~2022-11-04 12:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20 13:07 [dpdk-dev] [PATCH] mailmap: add a mailmap file to DPDK Bruce Richardson
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 [this message]
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=Y2UCnGtbUxRoSBqN@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --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 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.