From: Trevor Woerner <twoerner@gmail.com>
To: "Cetola, Stephano" <stephano.cetola@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"Orling, Timothy T" <timothy.t.orling@intel.com>,
OTC Embedded All <otc.embedded.all@intel.com>,
"Erway, Tracey M" <tracey.m.erway@intel.com>,
"Chan, Aaron Chun Yew" <aaron.chun.yew.chan@intel.com>
Subject: Re: Canceled: Yocto Project Technical Team Meeting
Date: Mon, 14 May 2018 19:36:01 -0400 [thread overview]
Message-ID: <CAHUNapTmUD1evY_RPFnb6eZZRJ3f_kwqNcbOUJ=22xw3wqQd9g@mail.gmail.com> (raw)
In-Reply-To: <1C72AF990F2FFD43A51A2896DAD431FC091F6DA3@ORSMSX109.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
Did the updated invite go out? I don't think I've seen it.
Is the meeting scheduled for May 15th?
On Thu, May 10, 2018 at 1:41 PM, Cetola, Stephano <stephano.cetola@intel.com
> wrote:
> Stephen will be sending an updated Technical Meeting invite shortly.
>
>
> Cheers,
> Stephano
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
[-- Attachment #2: Type: text/html, Size: 1187 bytes --]
next prev parent reply other threads:[~2018-05-14 23:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 17:41 Canceled: Yocto Project Technical Team Meeting Cetola, Stephano
2018-05-14 23:36 ` Trevor Woerner [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-03 15:08 Jolley, Stephen K
2018-05-24 21:55 Jolley, Stephen K
2018-05-24 21:55 Jolley, Stephen K
2015-09-01 16:10 Jolley, Stephen K
2014-12-16 0:07 Jolley, Stephen K
2014-04-22 21:32 Jolley, Stephen K
2013-12-30 17:14 Liu, Song
2013-01-28 23:08 Liu, Song
2013-01-28 23:08 Liu, Song
[not found] ` <51070930.8080608@linux.intel.com>
2013-01-28 23:29 ` Liu, Song
2012-07-09 17:43 Liu, Song
2012-07-09 17:43 Liu, Song
2012-02-10 22:27 Liu, Song
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='CAHUNapTmUD1evY_RPFnb6eZZRJ3f_kwqNcbOUJ=22xw3wqQd9g@mail.gmail.com' \
--to=twoerner@gmail.com \
--cc=aaron.chun.yew.chan@intel.com \
--cc=otc.embedded.all@intel.com \
--cc=stephano.cetola@intel.com \
--cc=timothy.t.orling@intel.com \
--cc=tracey.m.erway@intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.