kernelci.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Guillaume Tucker" <guillaume.tucker@collabora.com>
To: "kernelci@groups.io" <kernelci@groups.io>
Cc: helpdesk@kernel.org,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: KernelCI at lists.linux.dev
Date: Fri, 29 Jul 2022 17:06:09 +0200	[thread overview]
Message-ID: <76b71f49-d02e-c580-6b29-dd5ea21429c6@collabora.com> (raw)
In-Reply-To: <2ffe18c0-59cd-698c-93b8-974762ef27d1@collabora.com>

On 15/07/2022 07:12, Guillaume Tucker wrote:
> On 14/07/2022 16:51, Konstantin Ryabitsev wrote:
>> On Thu, Jul 14, 2022 at 10:26:57AM +0200, Guillaume Tucker wrote:
>>> Hello,
>>>
>>> The KernelCI community has been using kernelci@groups.io for a
>>> few years, however it's less than ideal as messages have to be
>>> moderated for all non-members.  Also we've been getting closer to
>>> the kernel community over the years and it isn't a great fit for
>>> that.  Would it be possible to create a kernelci@lists.linux.dev
>>> mailing list so we would then transition away from groups.io?
>>
>> For sure, I don't see why not. We can even import groups.io archives once the
>> migration is decided. If you do decide to move, just follow the procedure
>> described on
>> https://subspace.kernel.org/lists.linux.dev.html#requesting-list-hosting
> 
> Thank you, I've just done that now.

As we would like to move to the new list and stop using
groups.io, it would seem useful to also import the list of
subscribers from groups.io.  Please let me know if you don't want
to be subscribed to the new list by the end of next week (Aug 5).

I'll also send some messages on IRC and Slack to be sure everyone
knows about this.

Thanks,
Guillaume

  reply	other threads:[~2022-07-29 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  8:26 KernelCI at lists.linux.dev Guillaume Tucker
2022-07-14 14:51 ` Konstantin Ryabitsev
2022-07-15  5:12   ` Guillaume Tucker
2022-07-29 15:06     ` Guillaume Tucker [this message]
     [not found]     ` <1706552EEFF7A8A6.5263@groups.io>
2022-11-18 10:04       ` Guillaume Tucker

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=76b71f49-d02e-c580-6b29-dd5ea21429c6@collabora.com \
    --to=guillaume.tucker@collabora.com \
    --cc=helpdesk@kernel.org \
    --cc=kernelci@groups.io \
    --cc=konstantin@linuxfoundation.org \
    /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).