All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mailmap: add a mailmap file to DPDK
Date: Tue, 20 Oct 2020 17:17:58 +0200	[thread overview]
Message-ID: <1741910.NPnI57ggvb@thomas> (raw)
In-Reply-To: <20201020150322.GG558@bricha3-MOBL.ger.corp.intel.com>

20/10/2020 17:03, Bruce Richardson:
> On Tue, Oct 20, 2020 at 04:29:18PM +0200, Thomas Monjalon wrote:
> > 20/10/2020 15:07, Bruce Richardson:
> > > 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.
> > 
> > I agree it helps fixing typos in names, that's why I have such file.
> > To be really useful, we should add every contributors.
> 
> Surely not every contributor has multiple email addresses or their emails
> in multiple formats?
> 
> > > 
> > > 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.
> > 
> > Do you want me to write a v2?
> > 
> Feel free to. However, I think the contents should be limited to only those
> that need to be there.

Misunderstanding then.
The other usage I'm looking at, is your last sentence above:
"
It also helps fix up any mangled names, for example,
with surname/firstname reversed, or with incorrect capitalization.
"
This usage requires to have everyone listed.



  reply	other threads:[~2020-10-20 15:18 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 [this message]
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=1741910.NPnI57ggvb@thomas \
    --to=thomas@monjalon.net \
    --cc=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 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.