DPDK website maintenance
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "web@dpdk.org" <web@dpdk.org>
Cc: "events@dpdk.org" <events@dpdk.org>
Subject: Re: [dpdk-web] [dpdk-events] [PATCH] update 2017 events
Date: Tue, 11 Jul 2017 10:58:57 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA9B02FE52@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20170710214441.2264-1-thomas@monjalon.net>


> -----Original Message-----
> From: events [mailto:events-bounces@dpdk.org] On Behalf Of Thomas
> Monjalon
> Sent: Monday, July 10, 2017 10:45 PM
> To: web@dpdk.org
> Cc: events@dpdk.org
> Subject: [dpdk-events] [PATCH] update 2017 events
> 
> China Summit had not been announced on this page.
> It is now archived with India Summit.
> 
> The next events (Europe and USA) will be confirmed later.
> The dates have been agreed by the Governing Board.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>  events.html | 19 +++++++++++++++++--
>  1 file changed, 17 insertions(+), 2 deletions(-)
> 
> diff --git a/events.html b/events.html
> index 613ae84..4337e70 100644
> --- a/events.html
> +++ b/events.html
> @@ -39,11 +39,18 @@
>  			</nav>
>  		</header>
>  		<section id="events">
> -			<h2 id="indiasummit2017">&rsaquo; DPDK <em>Summit</em>,
> Bangalore - April 25-26, 2017</h2>
> +			<h2 id="usasummit2017">&rsaquo; DPDK <em>Summit</em>,
> San Jose - November 14-15, 2017</h2>
>  			<p style="text-align: center;">
>  				<a href="https://dpdksummit.com" class="button">
>  					<i class="material-icons">event_note</i>
> -					Register
> +					NOT YET CONFIRMED
> +				</a>
> +			</p>
> +			<h2 id="userspace2017">&rsaquo; DPDK <em>Userspace</em>,
> Dublin - September 26-27, 2017</h2>
> +			<p style="text-align: center;">
> +				<a href="https://dpdksummit.com" class="button">
> +					<i class="material-icons">event_note</i>
> +					NOT YET CONFIRMED
>  				</a>
>  			</p>
>  			<h3 id="SVmeetup">&rsaquo; DPDK <em>Meetup</em>, Silicon
> Valley - every 2<sup>nd</sup> Thursday</h3>
> @@ -53,6 +60,14 @@
>  			<p>
>  				<a
> href="http://www.meetup.com/DPDK_org">Register</a>
>  			</p>
> +			<h3 id="chinasummit2017">&rsaquo; DPDK <em>Summit</em>,
> Shanghai - June 27, 2017</h3>
> +			<p>
> +				<a href="http://dpdksummit.com/us/en/past-
> events">Archive</a>
> +			</p>
> +			<h3 id="indiasummit2017">&rsaquo; DPDK <em>Summit</em>,
> Bangalore - April 25-26, 2017</h3>
> +			<p>
> +				<a href="http://dpdksummit.com/us/en/past-
> events">Archive</a>
> +			</p>
>  			<h3 id="userspace2016">&rsaquo; DPDK <em>Userspace</em>,
> Dublin - October 20-21, 2016</h3>
>  			<p>
>  				<a href="http://dpdksummit.com/us/en/past-
> events">Archive</a>
> --
> 2.13.2

Acked-by: Tim O'Driscoll <tim.odriscoll@intel.com>

  reply	other threads:[~2017-07-11 10:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 21:44 [dpdk-web] " Thomas Monjalon
2017-07-11 10:58 ` O'Driscoll, Tim [this message]
2017-07-11 11:03   ` [dpdk-web] [dpdk-events] " 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=26FA93C7ED1EAA44AB77D62FBE1D27BA9B02FE52@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=events@dpdk.org \
    --cc=thomas@monjalon.net \
    --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).