All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: Re: [PATCH v6] mailmap: add file to DPDK
Date: Sun, 27 Nov 2022 11:27:13 +0100	[thread overview]
Message-ID: <3224328.VqM8IeB0Os@thomas> (raw)
In-Reply-To: <CH0PR11MB572449289959E2AB7A877094EB0E9@CH0PR11MB5724.namprd11.prod.outlook.com>

> > From: Bruce Richardson <bruce.richardson@intel.com>
> > 
> > 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".

and to do accurate automatic Cc with "get_maintainer.pl".

> > 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.
> > 
> > While at it, update our checkpatches.sh script and add some
> > documentation to help new contributors.
> > 
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> 
> <snip>
> 
> > +Cristian Dumitrescu <cristian.dumitrescu@intel.com> 
> <cristian.dumitrescu@yahoo.com>
> 
> The above yahoo.com address under my name was a mistake and it is not valid, therefore it should probably be removed from here.

Fixed

Acked-by: Thomas Monjalon <thomas@monjalon.net>

Added exception in devtools/check-spdx-tag.sh,

Applied, thanks.

Now we have a list of contributors :)



      reply	other threads:[~2022-11-27 10:27 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
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 [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=3224328.VqM8IeB0Os@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.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.