From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: printing-architecture@lists.linuxfoundation.org
Subject: Re: PSA: this list is moving to lists.linux.dev (no action required)
Date: Thu, 21 Dec 2023 15:30:03 -0500 [thread overview]
Message-ID: <CAMwyc-T=OzZoHz9iiM_hrDgqVjCMErrN50OhxSGRzRs4rZ7mxQ@mail.gmail.com> (raw)
In-Reply-To: <20231218-khaki-adder-from-eldorado-aa4f1a@lemur>
On Mon, 18 Dec 2023 at 18:02, Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
> The mailman-2 system running on lists.linuxfoundation.org is being
> decommissioned, so all lists currently hosted there will be found new homes.
>
> This Thursday, December 21, at 11AM PST (19:00 UTC), this list will be migrated
> to live on lists.linux.dev, but the impact of this move should be minor:
>
> 1. The new canonical list address will be printing-architecture@lists.linux.dev.
>
> 2. *The old address will continue to work* for the foreseeable future, so any
> existing conversations can continue and any new messages sent to the old
> list address will be properly delivered to all subscribers.
>
> 3. All members will be automatically subscribed to the new list, so no action
> is required on anyone's part to keep receiving list mail.
>
> 4. The list will be archived on https://lore.kernel.org/printing-architecture/
> with all prior archives automatically imported.
>
> 5. The List-ID header will change, regardless to which address the message is
> sent:
>
> before: List-Id: <printing-architecture.lists.linuxfoundation.org>
> after: List-Id: <printing-architecture.lists.linux.dev>
>
> You will need to update your filtering rules if you filter based on the
> contents of that header (on or after the migration date).
>
> 6. The mailman footer will no longer be added to message bodies and the
> subject will no longer be modified to insert [Printing-architecture]
> (because this violates DMARC).
>
> 7. Subscribing and unsubscribing will be done using the mlmmj supported
> commands, documented at https://subspace.kernel.org/subscribing.html
>
> Please let me know if you have any questions or concerns. I will follow up
> on Thursday after the migration has been completed.
Hello:
This work is complete and this message acts as a test to make sure
that everything is working properly. The list archives will be moved
later today.
Best regards,
Konstantin
next prev parent reply other threads:[~2023-12-21 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 23:02 [Printing-architecture] PSA: this list is moving to lists.linux.dev (no action required) Konstantin Ryabitsev
2023-12-18 23:46 ` Ira McDonald
2023-12-21 20:30 ` Konstantin Ryabitsev [this message]
2023-12-23 1:01 ` Till Kamppeter
-- strict thread matches above, loose matches on Subject: below --
2023-12-18 23:07 [Tech-board-discuss] " Konstantin Ryabitsev
2023-12-21 20:35 ` Konstantin Ryabitsev
2023-12-18 22:54 [LVFS] " Konstantin Ryabitsev
2023-12-21 20:21 ` Konstantin Ryabitsev
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='CAMwyc-T=OzZoHz9iiM_hrDgqVjCMErrN50OhxSGRzRs4rZ7mxQ@mail.gmail.com' \
--to=konstantin@linuxfoundation.org \
--cc=printing-architecture@lists.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 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.