From: "Soumya Guptha" <soumya.k.guptha@intel.com>
To: "announce@edk2.groups.io" <announce@edk2.groups.io>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Moving Community meeting to March 17
Date: Tue, 1 Mar 2022 19:00:26 +0000 [thread overview]
Message-ID: <BN0PR11MB5758E6E06B3B4BB6F858EE59A7029@BN0PR11MB5758.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 436 bytes --]
Dear Community members,
I am sending this email on behalf of Miki Demester, TianoCore Community Manager.
I have moved the TianoCore Community meeting from March 3rd to March 17th to accommodate conflicts.
Miki Demester is dealing with a family situation and will be communicating after her return.
Please sync your calendar to reflect the changes.
Thanks,
Soumya
Soumya Guptha
Firmware Ecosystem Enabling Manager
[-- Attachment #2: Type: text/html, Size: 2712 bytes --]
reply other threads:[~2022-03-01 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BN0PR11MB5758E6E06B3B4BB6F858EE59A7029@BN0PR11MB5758.namprd11.prod.outlook.com \
--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