DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jill Lovato <jlovato@linuxfoundation.org>,
	tdelanerolle@linuxfoundation.org
Cc: web@dpdk.org, events@dpdk.org
Subject: Re: [dpdk-web] events pages URLs
Date: Wed, 09 Dec 2020 19:22:05 +0100	[thread overview]
Message-ID: <1919490.N7aYvMAyfQ@thomas> (raw)
In-Reply-To: <7346439.5R9uWt43sf@thomas>

Please let's progress on this front.

11/11/2020 23:19, Thomas Monjalon:
> Hi,
> 
> I'm looking at the events pages:
> https://www.dpdk.org/event/dpdk-summit-san-francisco-2014/
> https://www.dpdk.org/event/dpdk-summit-beijing-2015/
> https://www.dpdk.org/event/dpdk-summit-san-francisco-2015/
> https://www.dpdk.org/event/dpdk-userspace-dublin-2015/
> https://www.dpdk.org/event/dpdk-summit-china-may-18-2016/
> https://www.dpdk.org/event/dpdk-summit-usa-2016/
> https://www.dpdk.org/event/dpdk-userspace-dublin-october-20-21-2016/
> https://www.dpdk.org/event/dpdk-summit-bangalore-2018/
> https://www.dpdk.org/event/dpdk-summit-china-2018/
> https://www.dpdk.org/event/dpdk-userspace-dublin-2018/
> https://www.dpdk.org/event/dpdk-summit-north-america-2018/
> https://www.dpdk.org/event/dpdk-summit-bangalore-2019/
> https://www.dpdk.org/event/dpdk-china-june-24th-2019/
> https://www.dpdk.org/event/dpdk-userspace-bordeaux/
> https://www.dpdk.org/event/dpdk-summit-na-mountain-view/
> https://www.dpdk.org/event/dpdk-userspace-summit/
> 
> Please would it be possible to rename some for consistency,
> while applying a common scheme with month and year?
> 
> The same request apply to the schedules in sched.com.
> 
> Thanks




  reply	other threads:[~2020-12-09 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-11 22:19 Thomas Monjalon
2020-12-09 18:22 ` Thomas Monjalon [this message]
2020-12-16 13:28   ` [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=1919490.N7aYvMAyfQ@thomas \
    --to=thomas@monjalon.net \
    --cc=events@dpdk.org \
    --cc=jlovato@linuxfoundation.org \
    --cc=tdelanerolle@linuxfoundation.org \
    --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).