From: Mitchell, Nathaniel P <nathaniel.p.mitchell@intel.com>
To: chipsec@lists.01.org
Subject: Community meeting 9/7/2022 @ 11am-noon PT
Date: Thu, 01 Sep 2022 23:24:34 +0000 [thread overview]
Message-ID: <CO1PR11MB486683F757373C7F21590A6CDD7B9@CO1PR11MB4866.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]
Hello Chipsec Community,
2 Notes:
1) The quarterly community meeting is coming up this next Wednesday, September 7th. If you would like to: join the conversation, learn about what's happened and what's planned or simply get some of your questions answered, please stop by! Details can be found on our wiki here: https://github.com/chipsec/chipsec/wiki/Community-Meetings
2) The lists.01.org mailing list service is being End of Lifed in the next few weeks. The plan is to migrate everything to lists.linuxfoundation.org. Keep an eye out for that change.
I look forward to seeing you in the meeting next week!
Thanks,
Nathaniel Mitchell
Security Researcher/Chipsec Developer
Foundational Software Technologies
Software and Advanced Technology Group
Intel Corporation
Confidentiality Notice | This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, immediately contact the sender by reply e-mail and destroy the original and all copies of the message.
PS if the time slot for the community meeting does not work for you but you want to be involved, please let me know and we can see about maybe alternating time slots to accommodate different geos.
[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 45091 bytes --]
reply other threads:[~2022-09-01 23:24 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-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=CO1PR11MB486683F757373C7F21590A6CDD7B9@CO1PR11MB4866.namprd11.prod.outlook.com \
--to=nathaniel.p.mitchell@intel.com \
--cc=chipsec@lists.01.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 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).