cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "Neal Caidin" <ncaidin@linuxfoundation.org>
To: cip-dev@lists.cip-project.org
Cc: "cip-members@lists.cip-project.org"
	<cip-members@lists.cip-project.org>,
	 "cip-board@lists.cip-project.org"
	<cip-board@lists.cip-project.org>,
	 "cip-security@lists.cip-project.org"
	<cip-security@lists.cip-project.org>
Subject: Password reset - Re: [cip-dev] [cip-members] Migration complete - Re: Mailman2 to Groups.io reminder
Date: Tue, 7 Apr 2020 07:39:26 -0400	[thread overview]
Message-ID: <CAODMxsJE97HXV68Jpj6Wd0D2D-HJVriBs=2uAVHGbGepoA6gcw@mail.gmail.com> (raw)
In-Reply-To: <610BEDF6-E16A-48BC-B8EE-BDBEA1846583@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 3574 bytes --]

For anybody who did not get a password reset email, you can go to
https://lists.cip-project.org/ , choose Login , and click the Forgot
Password link.

Best,
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 Tue, Apr 7, 2020 at 6:26 AM Urs Gleim <urs.gleim@siemens.com> wrote:

> Hi Neal,
>
> Thanks. However I was not requested to set a password.
>
> Best regards,
> Urs
>
> --
> Urs Gleim | Siemens AG | Corporate Technology
>
> Am 06.04.2020 um 23:45 schrieb Neal Caidin <ncaidin@linuxfoundation.org>:
>
> 
> Dear CIP Community,
>
> The migration is complete.
>
> You should receive an email shortly asking you to log in with your email
> address and set a password.
>
> One important note, please do NOT unsubscribe from the "main" list. This
> would unsubscribe you from all of the CIP lists. "main" is an
> administrative list used by Groups.io as a parent list to manage the other
> lists. Please let me know if you have any questions or issues.
>
> Lists
>
> https://lists.cip-project.org/main
>
>
>
> https://lists.cip-project.org/cip-board
>
> https://lists.cip-project.org/cip-dev
>
> https://lists.cip-project.org/cip-testing-results
>
> https://lists.cip-project.org/cip-members
>
> https://lists.cip-project.org/cip-security
>
>
>
> Email addresses
>
> cip-board@lists.cip-project.org
>
> cip-dev@lists.cip-project.org
>
> cip-testing-results@lists.cip-project.org
>
> cip-members@lists.cip-project.org <cip-members@lists.cip-projec.org>
>
> cip-security@lists.cip-project.org
>
> *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 Mon, Apr 6, 2020 at 3:34 PM Neal Caidin <ncaidin@linuxfoundation.org>
> wrote:
>
>> 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
>>>
>> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4563): https://lists.cip-project.org/g/cip-dev/message/4563
Mute This Topic: https://lists.cip-project.org/mt/72848146/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


[-- Attachment #2: Type: text/html, Size: 14668 bytes --]

  reply	other threads:[~2020-04-07 11:39 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
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       ` Neal Caidin [this message]
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='CAODMxsJE97HXV68Jpj6Wd0D2D-HJVriBs=2uAVHGbGepoA6gcw@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).