From: "Jörg Rödel" <joro@8bytes.org>
To: "Dong, Chuanxiao" <chuanxiao.dong@intel.com>
Cc: "svsm-devel@coconut-svsm.dev" <svsm-devel@coconut-svsm.dev>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>
Subject: Re: [svsm-devel] SVSM Development Call May 29th, 2024
Date: Wed, 29 May 2024 09:08:32 +0200 [thread overview]
Message-ID: <ZlbUcG0GRMOWV1dp@8bytes.org> (raw)
In-Reply-To: <BL3PR11MB64589F48AB63EA77FD06CDB38DF22@BL3PR11MB6458.namprd11.prod.outlook.com>
Hi Chuanxiao,
On Wed, May 29, 2024 at 12:15:11AM +0000, Dong, Chuanxiao wrote:
> Hello, just wondering if the meeting minutes published at
> https://github.com/coconut-svsm/governance/tree/main/Meetings are the
> recordings or there will be video/sound recordings published at
> somewhere else?
The recordings are currently not published, only the meeting minutes
(which are created from the transcripts).
Regards,
Joerg
next prev parent reply other threads:[~2024-05-29 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 20:05 SVSM Development Call May 29th, 2024 Jörg Rödel
2024-05-29 0:15 ` [svsm-devel] " Dong, Chuanxiao
2024-05-29 7:08 ` Jörg Rödel [this message]
2024-05-30 8:47 ` 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=ZlbUcG0GRMOWV1dp@8bytes.org \
--to=joro@8bytes.org \
--cc=chuanxiao.dong@intel.com \
--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 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).