From: "Jörg Rödel" <joro@8bytes.org>
To: svsm-devel@coconut-svsm.dev, linux-coco@lists.linux.dev
Subject: Re: [svsm-devel] Development Plan Document
Date: Thu, 16 May 2024 09:49:25 +0200 [thread overview]
Message-ID: <ZkW6hVW6F2KJqIpV@8bytes.org> (raw)
In-Reply-To: <Zj30Nqq3OS58DwpP@8bytes.org>
Hi,
On Fri, May 10, 2024 at 12:17:26PM +0200, Jörg Rödel wrote:
> As announced in the last meeting I am sharing a development plan
> document which lists the in-progress and future work items to get
> COCONUT-SVSM to the envisioned point.
As discussed in the last meeting, I opened a PR adding the document to
the SVSM repository. Find the PR here:
https://github.com/coconut-svsm/svsm/pull/344
Regards,
Joerg
prev parent reply other threads:[~2024-05-16 7:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 10:17 Development Plan Document Jörg Rödel
2024-05-14 9:06 ` [svsm-devel] " Jörg Rödel
2024-05-15 10:20 ` Reshetova, Elena
2024-05-15 11:59 ` Carlos López
2024-05-15 12:04 ` Reshetova, Elena
2024-05-15 12:14 ` Jörg Rödel
2024-05-17 10:01 ` Reshetova, Elena
2024-05-23 9:52 ` Jörg Rödel
2024-05-16 7:49 ` Jörg Rödel [this message]
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=ZkW6hVW6F2KJqIpV@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 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).