From: Shreyansh Jain <shreyansh.jain@nxp.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: Wed, 2 Nov 2016 07:29:07 +0000 [thread overview]
Message-ID: <DB5PR0401MB2054393795D79131A41F3F4090A00@DB5PR0401MB2054.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA6760AAE9@IRSMSX108.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
Hello,
Apologies for not being able to attend the first call.
3PM GMT on either of Tuesday or Monday is fine with me for the next call.
Though 3PM GMT would be comfortable, but 4PM GST wouldn't be a problem either.
-
Shreyansh
From: moving [mailto:moving-bounces@dpdk.org] On Behalf Of O'Driscoll, Tim
Sent: Tuesday, November 01, 2016 5:34 PM
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
[-- Attachment #2: Type: text/html, Size: 3851 bytes --]
prev parent reply other threads:[~2016-11-02 7:29 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
2016-11-02 7:29 ` Shreyansh Jain [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=DB5PR0401MB2054393795D79131A41F3F4090A00@DB5PR0401MB2054.eurprd04.prod.outlook.com \
--to=shreyansh.jain@nxp.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).