From: "O'driscoll, Tim" <tim.o'driscoll@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Community Call, Monday 2nd February, 17:00 GMT
Date: Wed, 21 Jan 2015 09:45:55 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA54CA6F0F@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <20150120091058.08e87f6e@urahara>
> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Tuesday, January 20, 2015 5:11 PM
> To: O'driscoll, Tim
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] DPDK Community Call, Monday 2nd February, 17:00
> GMT
>
> On Tue, 20 Jan 2015 15:21:40 +0000
> "O'driscoll, Tim" <tim.o'driscoll@intel.com> wrote:
>
> > We had our last community call in December, and then took a break over
> the holiday period. I think we should reinstate these, so I've scheduled the
> next one for Monday 2nd February. Since our last call was at a time
> convenient for Asia, this one is at a time that's more convenient for people
> based in the USA. As for previous calls, I'll post a recording to youtube
> afterwards for anybody who can't make it.
> >
> > I don't have an agenda yet, but will send one out in advance of the
> meeting.
>
> This is right after FOSDEM and many people will be returning home.
Good point. Thanks for pointing this out. I'll move the meeting to avoid this clash.
Tim
next prev parent reply other threads:[~2015-01-21 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 15:21 O'driscoll, Tim
2015-01-20 17:10 ` Stephen Hemminger
2015-01-21 9:45 ` O'driscoll, Tim [this message]
2015-01-21 14:39 ` O'driscoll, Tim
2015-01-21 19:53 ` Stephen Hemminger
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=26FA93C7ED1EAA44AB77D62FBE1D27BA54CA6F0F@IRSMSX102.ger.corp.intel.com \
--to=tim.o'driscoll@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).