From: Marc Zyngier <maz@kernel.org>
To: kvmarm <kvmarm@lists.cs.columbia.edu>
Subject: [REPOST][URGENT] kvmarm mailing list migration
Date: Thu, 13 Oct 2022 16:09:20 +0100 [thread overview]
Message-ID: <86edvbg3q7.wl-maz@kernel.org> (raw)
[Reposting this, as it has been almost two weeks since the initial
announcement and we're still at sub-10% of the users having
subscribed to the new list]
Hi all,
As you probably all know, the kvmarm mailing has been hosted on
Columbia's machines for as long as the project existed (over 13
years). After all this time, the university has decided to retire the
list infrastructure and asked us to find a new hosting.
A new mailing list has been created on lists.linux.dev[1], and I'm
kindly asking everyone interested in following the KVM/arm64
developments to start subscribing to it (and start posting your
patches there). I hope that people will move over to it quickly enough
that we can soon give Columbia the green light to turn their systems
off.
Note that the new list will only get archived automatically once we
fully switch over, but I'll make sure we fill any gap and not lose any
message. In the meantime, please Cc both lists.
I would like to thank Columbia University for their long lasting
support and willingness to help during this transition, as well as
Konstantin (and the kernel.org crew) for quickly stepping up to the
challenge and giving us a new home!
Thanks,
M.
[1] https://subspace.kernel.org/lists.linux.dev.html
--
Without deviation from the norm, progress is not possible.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next reply other threads:[~2022-10-13 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 15:09 Marc Zyngier [this message]
2022-10-14 10:41 ` [REPOST][URGENT] kvmarm mailing list migration Mark Rutland
2022-10-28 0:36 ` Oliver Upton
2022-10-28 11:20 ` Marc Zyngier
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=86edvbg3q7.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
/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.