DPDK CI discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Jeremy Plsek <jplsek@iol.unh.edu>, "ci@dpdk.org" <ci@dpdk.org>,
	"marketing@dpdk.org" <marketing@dpdk.org>
Subject: Re: [dpdk-ci] [dpdk-marketing]  Results are now public
Date: Fri, 09 Nov 2018 15:01:42 +0100	[thread overview]
Message-ID: <1728520.EjkXxhgpI8@xps> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77AF03B@IRSMSX108.ger.corp.intel.com>

09/11/2018 14:58, O'Driscoll, Tim:
> From: Thomas Monjalon
> > 08/11/2018 14:01, Ferruh Yigit:
> > > On 11/7/2018 7:30 AM, Thomas Monjalon wrote:
> > > > 06/11/2018 16:33, Jeremy Plsek:
> > > >> Hi all,
> > > >>
> > > >> This is just an update that all detailed results are now public.
> > > >>
> > > >> If there is anything out of place, feel free to let me know!
> > > >
> > > > It is really nice!
> > > > Thank you
> > >
> > > Should we announce this in 'announce' or 'dev' mail lists? Many people
> > not aware
> > > of this.
> > 
> > It deserves an announce.
> > And even a blog post I guess.
> > +Cc marketing team
> 
> Agreed. I can do a quick post to announce@dpdk.org. I believe Jeremy is working on a blog post which can provide more detail.

Should we wait to have a blog post and reference it in the announce?

  reply	other threads:[~2018-11-09 14:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 15:33 [dpdk-ci] " Jeremy Plsek
2018-11-07  7:30 ` Thomas Monjalon
2018-11-08 13:01   ` Ferruh Yigit
2018-11-08 13:10     ` Thomas Monjalon
2018-11-08 13:16       ` [dpdk-ci] [dpdk-marketing] " Trishan de Lanerolle
2018-11-08 13:37         ` Thomas Monjalon
2018-11-08 15:57         ` Jeremy Plsek
2018-11-09 13:58       ` O'Driscoll, Tim
2018-11-09 14:01         ` Thomas Monjalon [this message]
2018-11-09 14:07           ` Trishan de Lanerolle
2018-11-09 14:08           ` O'Driscoll, Tim
2018-11-09 15:03             ` Jeremy Plsek
2018-11-14 21:07               ` Jeremy Plsek
2018-11-14 22:16                 ` Thomas Monjalon
2018-11-15 22:13                   ` O'Driscoll, Tim
2018-11-15 22:30                     ` Jill Lovato
2018-11-16  2:29                     ` Tu, Lijuan
2018-11-16  2:48                       ` Lincoln Lavoie
2018-11-16 16:42                         ` Jill Lovato
2018-11-19 15:08                           ` Mara Bernazzani
2018-11-19 17:48                             ` Jill Lovato
2018-11-19 17:52                               ` Lincoln Lavoie
2018-11-19 17:55                                 ` Jill Lovato
2018-11-20  9:40                                   ` Thomas Monjalon
2018-11-20 13:58                                   ` O'Driscoll, Tim
2018-11-20 15:35                                     ` Jeremy Plsek

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=1728520.EjkXxhgpI8@xps \
    --to=thomas@monjalon.net \
    --cc=ci@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jplsek@iol.unh.edu \
    --cc=marketing@dpdk.org \
    --cc=tim.odriscoll@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).