From: Thomas Monjalon <thomas@monjalon.net>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [pull-request] next-pipeline 18.11 PRE-RC1
Date: Sun, 14 Oct 2018 12:52:13 +0200 [thread overview]
Message-ID: <3061777.9qk3oM9taa@xps> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891268E7D8ABD@IRSMSX107.ger.corp.intel.com>
12/10/2018 13:07, Dumitrescu, Cristian:
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > 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.
Thanks for fixing compilation and nits.
next-pipeline is pulled in master.
prev parent reply other threads:[~2018-10-14 10:52 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
2018-10-14 10:52 ` 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=3061777.9qk3oM9taa@xps \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@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 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).