From: Matt Spencer <Matt.Spencer@arm.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
"moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] Time for next week's meeting
Date: Tue, 1 Nov 2016 16:09:03 +0000 [thread overview]
Message-ID: <VI1PR0801MB2062F0EF40515BD6CE632BB895A10@VI1PR0801MB2062.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA6760AAE9@IRSMSX108.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
I am going to be in SFO on Tuesday next week, I am assuming the meeting will be at 7am in SFO? That will be fine for me as the jet-lag will mean I got up at 3am anyway!
Looking forward to chatting next week.
/Matt
________________________________
From: moving <moving-bounces@dpdk.org> on behalf of O'Driscoll, Tim <tim.odriscoll@intel.com>
Sent: 01 November 2016 12:03:40
To: moving@dpdk.org
Subject: [dpdk-moving] Time for next week's meeting
At yesterday's call we discussed having our next meeting at 4pm GMT/5pm CET/11am EST/8am PST next Tuesday (Nov 8th). After the meeting, I got one request to move this another hour earlier to 3pm GMT/4pm CET/10am EST/7am PST. Which time works best for people next Tuesday? We'll go with whatever the majority answer is.
Tim
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
[-- Attachment #2: Type: text/html, Size: 3410 bytes --]
next prev parent reply other threads:[~2016-11-01 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 12:03 O'Driscoll, Tim
2016-11-01 16:09 ` Matt Spencer [this message]
2016-11-02 7:29 ` Shreyansh Jain
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=VI1PR0801MB2062F0EF40515BD6CE632BB895A10@VI1PR0801MB2062.eurprd08.prod.outlook.com \
--to=matt.spencer@arm.com \
--cc=moving@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).