From: Thomas Monjalon <thomas@monjalon.net>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: web@dpdk.org
Subject: Re: [dpdk-web] [PATCH] confirm userspace summit 2017
Date: Wed, 02 Aug 2017 11:41:36 +0200 [thread overview]
Message-ID: <4201341.fHsfjDtMQv@xps> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23ED58238@IRSMSX103.ger.corp.intel.com>
02/08/2017 10:47, Mcnamara, John:
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > 02/08/2017 10:16, Mcnamara, John:
> > > From: Thomas Monjalon
> > > >
> > > > http://dpdk.org/ml/archives/announce/2017-July/000138.html
> > > >
> > > > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > > > ---
> > > > events.html | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/events.html b/events.html index d7b7457..097fa9a 100644
> > > > --- a/events.html
> > > > +++ b/events.html
> > > > @@ -50,7 +50,7 @@
> > > > <p style="text-align: center;">
> > > > <a href="https://dpdksummit.com" class="button">
> > > > <i class="material-icons">event_note</i>
> > > > - NOT YET CONFIRMED
> > > > + Register
> > >
> > > Maybe "Register" would be better as a link:
> > > https://dpdksummit.com/us/en/registration-userspace
> >
> > Yes but from this page, there is no obvious link to the description of the
> > event.
> > Is it fine like that or do you prefer more links?
>
> You are correct. May it is better to just link to the events page. The registration is very clear from there:
>
> https://dpdksummit.com/us/en/events
Good idea
Applied with above link:
http://dpdk.org/events
prev parent reply other threads:[~2017-08-02 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 20:45 Thomas Monjalon
2017-08-02 8:16 ` Mcnamara, John
2017-08-02 8:28 ` Thomas Monjalon
2017-08-02 8:47 ` Mcnamara, John
2017-08-02 9:41 ` 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=4201341.fHsfjDtMQv@xps \
--to=thomas@monjalon.net \
--cc=john.mcnamara@intel.com \
--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).