From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 59A8C2BA5 for ; Tue, 1 Nov 2016 13:03:43 +0100 (CET) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga105.jf.intel.com with ESMTP; 01 Nov 2016 05:03:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,579,1473145200"; d="scan'208,217";a="1053476682" Received: from irsmsx151.ger.corp.intel.com ([163.33.192.59]) by orsmga001.jf.intel.com with ESMTP; 01 Nov 2016 05:03:42 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.210]) by IRSMSX151.ger.corp.intel.com ([169.254.4.28]) with mapi id 14.03.0248.002; Tue, 1 Nov 2016 12:03:41 +0000 From: "O'Driscoll, Tim" To: "moving@dpdk.org" Thread-Topic: Time for next week's meeting Thread-Index: AdI0N4TkqlUcrG0MRB+6p32VusfwQw== Date: Tue, 1 Nov 2016 12:03:40 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA6760AAE9@IRSMSX108.ger.corp.intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMTc3OWIzNDItZGU3Yy00ZDhiLWE2MzQtNGFjNTVjMGE5NDZiIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IlB2M1RkRGswVnRWRVF6T2FIWUlPQk5jQXNrVVUyRjE4cGFldDF5QkdtVFU9In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.181] Content-Type: multipart/alternative; boundary="_000_26FA93C7ED1EAA44AB77D62FBE1D27BA6760AAE9IRSMSX108gercor_" MIME-Version: 1.0 Subject: [dpdk-moving] Time for next week's meeting X-BeenThere: moving@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK community structure changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2016 12:03:45 -0000 --_000_26FA93C7ED1EAA44AB77D62FBE1D27BA6760AAE9IRSMSX108gercor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 requ= est 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 m= ajority answer is. Tim --_000_26FA93C7ED1EAA44AB77D62FBE1D27BA6760AAE9IRSMSX108gercor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

At yesterday’s call we discussed having our ne= xt meeting at 4pm GMT/5pm CET/11am EST/8am PST next Tuesday (Nov 8th). Afte= r the meeting, I got one request to move this another hour earlier to 3pm G= MT/4pm CET/10am EST/7am PST. Which time works best for people next Tuesday? We’ll go with whatever the major= ity answer is.

 


Tim

 

--_000_26FA93C7ED1EAA44AB77D62FBE1D27BA6760AAE9IRSMSX108gercor_--