From: Joseph Reynolds <jrey@linux.ibm.com>
To: Andrew Jeffery <andrew@aj.id.au>, openbmc <openbmc@lists.ozlabs.org>
Subject: Re: Security Working Group meeting - Wednesday August 17
Date: Wed, 17 Aug 2022 11:13:31 -0500 [thread overview]
Message-ID: <7f7f8fb1-0bb0-d453-e96c-8f8e40f7b3d7@linux.ibm.com> (raw)
In-Reply-To: <61158439-f152-4399-86f8-a4f730dd967b@www.fastmail.com>
On 8/17/22 12:11 AM, Andrew Jeffery wrote:
>
> On Wed, 17 Aug 2022, at 12:37, Joseph Reynolds wrote:
>> This is a reminder of the OpenBMC Security Working Group meeting
>> scheduled for this Wednesday August 17 at 10:00am PDT.
> Given the discussion from last meeting, is this on Discord?
No. The meeting access for Aug 17 is the same as before:
https://ibm.webex.com/meet/joseph.reynolds1
I wanted to give a couple of weeks notice (A) for attendees to firm up
any objections to moving, and (B) to announce the change.
Joseph
>
> Andrew
next prev parent reply other threads:[~2022-08-17 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 3:07 Security Working Group meeting - Wednesday August 17 Joseph Reynolds
2022-08-17 5:11 ` Andrew Jeffery
2022-08-17 16:13 ` Joseph Reynolds [this message]
2022-08-17 16:57 ` Brad Bishop
2022-08-17 20:11 ` Joseph Reynolds
2022-08-17 20:26 ` Security Working Group meeting - moved to Discord Voice channel Joseph Reynolds
2023-08-28 19:56 ` Security Working Group meeting - regular meetings discontinued Joseph Reynolds
2022-08-17 20:29 ` Security Working Group meeting - Wednesday August 17 Patrick Williams
-- strict thread matches above, loose matches on Subject: below --
2022-08-17 17:40 Nick Rivers
2022-08-17 17:47 ` Brad Bishop
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=7f7f8fb1-0bb0-d453-e96c-8f8e40f7b3d7@linux.ibm.com \
--to=jrey@linux.ibm.com \
--cc=andrew@aj.id.au \
--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 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.