From: "Jörg Rödel" <jroedel@suse.de>
To: amd-sev-snp@lists.suse.com, linux-coco@lists.linux.dev
Subject: [ANNOUNCE] SVSM development mailing list
Date: Tue, 22 Aug 2023 10:31:50 +0200 [thread overview]
Message-ID: <ZORyduBLCO-QEJKE@suse.de> (raw)
Hi,
I'd to invite everyone interested in the development of
Coconut-SVSM to join the newly created svsm-devel mailing list. The list
address is
svsm-devel@coconut-svsm.dev
It is hosted by mailman, the link to subscribe is
https://mail.8bytes.org/cgi-bin/mailman/listinfo/svsm-devel
The list will be used as an addition to GitHub for discussions on the
further development of the Coconut-SVSM project.
The archives are public, so please do not post any confidential or NDA
content to this list.
Regards,
--
Jörg Rödel
jroedel@suse.de
SUSE Software Solutions Germany GmbH
Frankenstraße 146
90461 Nürnberg
Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
next reply other threads:[~2023-08-22 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 8:31 Jörg Rödel [this message]
2023-08-23 9:22 ` [ANNOUNCE] SVSM development mailing list Alexey Kardashevskiy
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=ZORyduBLCO-QEJKE@suse.de \
--to=jroedel@suse.de \
--cc=amd-sev-snp@lists.suse.com \
--cc=linux-coco@lists.linux.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 read-only IMAP folder(s) and NNTP newsgroup(s).