From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: kvmarm <kvmarm@lists.cs.columbia.edu>
Subject: Re: [REPOST][URGENT] kvmarm mailing list migration
Date: Fri, 28 Oct 2022 12:20:20 +0100 [thread overview]
Message-ID: <364100e884023234e4ab9e525774d427@kernel.org> (raw)
In-Reply-To: <Y1skH3k6SIV0hEMZ@google.com>
On 2022-10-28 01:36, Oliver Upton wrote:
> On Thu, Oct 13, 2022 at 04:09:20PM +0100, Marc Zyngier wrote:
>> [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.
>
> Just wanted to explicitly highlight this point... can folks please
> continue to Cc the old list until we migrate to the new one?
> lore.kernel.org archives *only* contain mail sent to the columbia.edu
> address right now.
>
> Fortunately, the series I'm aware of that didn't do this still hit
> another archived list so I could find it with a bit more digging.
>
> Marc -- any idea when we're going to finally switch to the new world?
Given the amount of spam I'm dealing with on the Columbia list,
I'm tempted to say "real soon now".
I'll repeat my call for migration again next week, give it another
week, then ask Konstantin to switch the archives over to the new
list. This can take up to a week, but as soon as it is done,
I'll place the list under full moderation and ask Columbia to
kill it.
So it looks like we're looking at a ~2 week deadline. Should anyone
object to this plan, shout now!
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
prev parent reply other threads:[~2022-10-28 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 15:09 [REPOST][URGENT] kvmarm mailing list migration Marc Zyngier
2022-10-14 10:41 ` Mark Rutland
2022-10-28 0:36 ` Oliver Upton
2022-10-28 11:20 ` Marc Zyngier [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=364100e884023234e4ab9e525774d427@kernel.org \
--to=maz@kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=oliver.upton@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 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.