From: Parth Shukla <timevortex@google.com>
To: openbmc@lists.ozlabs.org
Subject: Security Working Group Meeting - Wed 30 September
Date: Tue, 29 Sep 2020 19:52:07 +0200 [thread overview]
Message-ID: <CAC1Cx+sLnCCWG3UVqaO0ohpsy4ggTQvzQhZHJQBV+EUYb33cQw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
This is a reminder of the OpenBMC Security Working Group meeting scheduled
for this Wednesday September 30 at 10:00am PDT.
There are currently no items on the agenda
<https://docs.google.com/document/d/1b7x9BaxsfcukQDqbvZsU2ehMq4xoJRQvLxxsDUWmAOI/edit>.
Assuming no items are added before the meeting then we have the option of
1) cancelling or 2) joining to see if anyone wants to bring up any topics
for discussion. What are people's preferences?
I'll assume option 2 as the default and dial in unless we get some
consensus on this thread to cancel the meeting instead.
Access, and notes are in the wiki:
https://github.com/openbmc/openbmc/wiki/Security-working-group
Regards,
Parth
[-- Attachment #2: Type: text/html, Size: 962 bytes --]
next reply other threads:[~2020-09-29 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 17:52 Parth Shukla [this message]
2020-09-30 18:56 ` Security Working Group Meeting - Wed 30 September - results Joseph Reynolds
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=CAC1Cx+sLnCCWG3UVqaO0ohpsy4ggTQvzQhZHJQBV+EUYb33cQw@mail.gmail.com \
--to=timevortex@google.com \
--cc=openbmc@lists.ozlabs.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).