From: "Jörg Rödel" <joro@8bytes.org>
To: svsm-devel@coconut-svsm.dev, linux-coco@lists.linux.dev
Subject: SVSM Development Call April 3rd, 2024
Date: Wed, 3 Apr 2024 13:20:19 +0200 [thread overview]
Message-ID: <Zg07c6Y5a_Ak5oXs@8bytes.org> (raw)
Hi,
Here is the usual call for agenda items for this weeks SVSM development
call. My agenda so far is:
* vTPM merge fallout
* Security issue mitigations
The items we can not cover during the meeting will be deferred to the
next meeting.
Please note that Europe is now also on summer time, so the meeting will
be at its usual time spot again. The definitive time is always in the
Google calendar I shared below.
Details of the meeting (GMeet and Calendar links, meeting time) can be
found in our governance repository at:
https://github.com/coconut-svsm/governance
The meeting will be recorded and the recording eventually published.
See you all there.
Regards,
Jörg
next reply other threads:[~2024-04-03 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 11:20 Jörg Rödel [this message]
2024-04-03 11:59 ` SVSM Development Call April 3rd, 2024 Yao, Jiewen
2024-04-03 12:18 ` James Bottomley
2024-04-03 13:11 ` Yao, Jiewen
2024-04-03 17:06 ` [svsm-devel] " Stefano Garzarella
2024-04-04 8:04 ` Jörg Rödel
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=Zg07c6Y5a_Ak5oXs@8bytes.org \
--to=joro@8bytes.org \
--cc=linux-coco@lists.linux.dev \
--cc=svsm-devel@coconut-svsm.dev \
/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.