DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [pull-request] next-pipeline 18.11 PRE-RC1
Date: Fri, 12 Oct 2018 11:07:25 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E7D8ABD@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <3740447.zQdSQcv5Hm@xps>



> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Friday, October 12, 2018 11:14 AM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [pull-request] next-pipeline 18.11 PRE-RC1
> 
> 01/10/2018 19:30, Cristian Dumitrescu:
> >   http://dpdk.org/git/next/dpdk-next-pipeline
> 
> Please, could you fix the names in author fields and signed-off, etc?
> Example: "Zhang, Roy Fan" should be "Fan Zhang
> <roy.fan.zhang@intel.com>"
> The idea is to keep the same exact name along the git history.
> 
> Thanks
> 

Done, thanks Thomas.

  reply	other threads:[~2018-10-12 11:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 17:30 Cristian Dumitrescu
2018-10-12 10:14 ` Thomas Monjalon
2018-10-12 11:07   ` Dumitrescu, Cristian [this message]
2018-10-14 10:52     ` 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=3EB4FA525960D640B5BDFFD6A3D891268E7D8ABD@IRSMSX107.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.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 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).