From: Neal Caidin <ncaidin@linuxfoundation.org>
To: cip-board@lists.cip-project.org,
cip-members@lists.cip-project.org,
cip-security@lists.cip-project.org,
cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] Mailman2 to Groups.io reminder
Date: Mon, 6 Apr 2020 15:34:26 -0400 [thread overview]
Message-ID: <CAODMxsJ5anJK+heh9rnWtAsvCCFLhVnm40cffABgG686_312mQ@mail.gmail.com> (raw)
In-Reply-To: <CAODMxsK_vgo-=FikL1Z2iYXtetRh+KpRJNL4MchmfXvLMqBTUA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 994 bytes --]
Reminder. Mailman2 to Groups.io conversion about to kick off (about an 1
1/2 hours from now).
Please see schedule below.
Best Regards,
Neal
*Neal Caidin*
Program Manager, Program Management & Operations
The Linux Foundation
+1 (919) 238-9104 (w/h)
+1 (919) 949-1861 (m)
ncaidin@linuxfoundation.org
On Thu, Apr 2, 2020 at 4:56 PM Neal Caidin <ncaidin@linuxfoundation.org>
wrote:
> [cross posted]
>
> Reminder. Mailman2 to Groups.io email is scheduled to start on
>
> Pacific - 2 pm , Monday, April 6
> Eastern - 5 pm, Monday April 6
> CET - 11 pm, Monday April 6
> JST - 6 am, Tuesday, April 7
>
> It is expected to take several hours, but could be as much as a full 24
> hours.
>
> When the migration is completed, I will send out the links so that you can
> access email archives.
>
> Best regards,
> Neal
>
>
> *Neal Caidin*
> Program Manager, Program Management & Operations
> The Linux Foundation
> +1 (919) 238-9104 (w/h)
> +1 (919) 949-1861 (m)
> ncaidin@linuxfoundation.org
>
[-- Attachment #1.2: Type: text/html, Size: 3207 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev
next prev parent reply other threads:[~2020-04-06 19:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 20:56 [cip-dev] Mailman2 to Groups.io reminder Neal Caidin
2020-04-06 19:34 ` Neal Caidin [this message]
2020-04-06 21:45 ` [cip-dev] Migration complete - " Neal Caidin
2020-04-06 22:43 ` Pavel Machek
2020-04-07 1:44 ` punit1.agrawal
2020-04-07 6:58 ` [cip-members] " Jan Kiszka
2020-04-07 15:12 ` Konstantin Ryabitsev
2020-04-07 15:17 ` Jan Kiszka
2020-04-07 15:40 ` Neal Caidin
2020-04-20 18:54 ` Pavel Machek
2020-04-07 7:09 ` Pavel Machek
2020-04-07 7:18 ` [cip-dev] [cip-members] " Chris Paterson
2020-04-07 10:26 ` Urs Gleim
2020-04-07 11:39 ` Password reset - " Neal Caidin
2020-04-09 15:26 ` Chris Paterson
2020-04-09 17:17 ` [cip-dev] [cip-board] " Neal Caidin
2020-04-20 13:50 ` [cip-dev] " Neal Caidin
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=CAODMxsJ5anJK+heh9rnWtAsvCCFLhVnm40cffABgG686_312mQ@mail.gmail.com \
--to=ncaidin@linuxfoundation.org \
--cc=cip-board@lists.cip-project.org \
--cc=cip-dev@lists.cip-project.org \
--cc=cip-members@lists.cip-project.org \
--cc=cip-security@lists.cip-project.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).