From: Rebecca Cran <rebecca@bluestop.org>
To: stephano <stephano.cetola@linux.intel.com>,
edk2-devel@lists.01.org, Laszlo Ersek <lersek@redhat.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
Andrew Fish <afish@apple.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Doran, Mark" <mark.doran@intel.com>,
"Richardson, Brian" <brian.richardson@intel.com>
Subject: Re: Event Invitation: TianoCore Community Meeting - NAMO / EMEA
Date: Fri, 5 Oct 2018 14:43:30 -0600 [thread overview]
Message-ID: <36beb58f-94f2-cd9f-b954-bfc0d15594c5@bluestop.org> (raw)
In-Reply-To: <6f50830d-ae37-8993-e773-ef530ff02fc0@linux.intel.com>
I don't see any information about time/place/etc. - should there be an
attachment?
On 10/5/18 1:39 PM, stephano wrote:
> stephano <stephano.cetola@linux.intel.com> has invited you to TianoCore Community Meeting - NAMO / EMEA
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-10-05 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 19:39 Event Invitation: TianoCore Community Meeting - NAMO / EMEA stephano
2018-10-05 20:43 ` Rebecca Cran [this message]
2018-10-05 22:29 ` stephano
2018-10-08 11:01 ` Laszlo Ersek
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-list 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=36beb58f-94f2-cd9f-b954-bfc0d15594c5@bluestop.org \
--to=devel@edk2.groups.io \
/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