From: Thomas Monjalon <thomas@monjalon.net>
To: Yevgeny Kliteynik <kliteyn@nvidia.com>
Cc: viacheslavo@nvidia.com, suanmingm@nvidia.com, dev@dpdk.org,
orika@nvidia.com
Subject: Re: [PATCH] Update mailmap file
Date: Thu, 12 Jan 2023 17:26:53 +0100 [thread overview]
Message-ID: <4527988.ejJDZkT8p0@thomas> (raw)
In-Reply-To: <20230112150350.20192-1-kliteyn@nvidia.com>
12/01/2023 16:03, Yevgeny Kliteynik:
> +Yevgeny Kliteynik <kliteyn@nvidia.com> <kliteyn@gmail.com>
Your nvidia.com email should be enough.
Please update this file in your first patch, it's enough.
next prev parent reply other threads:[~2023-01-12 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 15:03 Yevgeny Kliteynik
2023-01-12 16:26 ` Thomas Monjalon [this message]
2023-01-15 13:33 ` Yevgeny Kliteynik
2023-01-15 14:25 ` Yevgeny Kliteynik
2023-01-15 13:20 ` [PATCH v2] " Yevgeny Kliteynik
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=4527988.ejJDZkT8p0@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=kliteyn@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.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 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).