From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Lynch, Michael A" <michael.a.lynch@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Merge with 1.5.0??
Date: Fri, 27 Sep 2013 12:13:02 +0200 [thread overview]
Message-ID: <201309271213.02528.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <69D4F1CAB263EA44A83BF67D2ECDA25519C4C5C7@IRSMSX103.ger.corp.intel.com>
27/09/2013 11:22, Lynch, Michael A :
> Intel has now posted Intel DPDK R1.5.0 to our site, so it can be picked up
> by dpdk.org. See: www.intel/com/go/dpdk
Thanks for these new features.
It takes time to analyze for git formatting into commits.
Merge with community enhancements is in progress.
It will be announced soon.
> This e-mail and any attachments may contain confidential material for the
> sole use of the intended recipient(s). Any review or distribution by
> others is strictly prohibited. If you are not the intended recipient,
> please contact the sender and delete all copies.
Please do not put any confidential disclaimer on this mailing-list.
It cannot be confidential.
--
Thomas
prev parent reply other threads:[~2013-09-27 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 2:21 Jim Jia
2013-09-27 9:22 ` Lynch, Michael A
2013-09-27 10:13 ` 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=201309271213.02528.thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=michael.a.lynch@intel.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).