From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Richard Cziva <rc@richard.systems>
Cc: web@dpdk.org
Subject: Re: [dpdk-web] [PATCH 1/1] news update
Date: Fri, 24 Feb 2017 09:44:02 +0100 [thread overview]
Message-ID: <3668887.v0CeXbIRCT@xps13> (raw)
In-Reply-To: <20170223172918.38354-1-rc@richard.systems>
2017-02-23 17:29, Richard Cziva:
> --- a/news.html
> +++ b/news.html
> @@ -40,6 +40,10 @@
> <h2>In the News</h2>
> <ul>
> <li>
> + <em>February 23, 2017</em>
The date of the article is January 26th, 2017.
I think we should use this one.
> + <a href="https://reannz.co.nz/news/ruru-visualise-international-traffic-flows-real-time/">
> + REANNZ presents Ruru, a DPDK-based toolkit to visualise international traffic flows in real-time</a>
> + <li>
Thanks
Feel free to send an announce on announce@dpdk.org.
next prev parent reply other threads:[~2017-02-24 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 17:29 Richard Cziva
2017-02-24 8:44 ` Thomas Monjalon [this message]
2017-02-24 10:02 ` Richard Cziva
2017-02-26 17:03 ` 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=3668887.v0CeXbIRCT@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=rc@richard.systems \
--cc=web@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).