The future of our mailing lists
Hello S?bastien and co,
Following the announcement of alioth-lists.debian.net <http://alioth-lists.debian.net/> I got emails for pkg-common-lisp-commits at lists.alioth.debian.org <mailto:pkg-common-lisp-commits at lists.alioth.debian.org> and pkg-common-lisp-devel at lists.alioth.debian.org <mailto:pkg-common-lisp-devel at lists.alioth.debian.org>, see:
> Dear list owner,
>
> As per the announcement on debian-devel-announce[1] the migration of
> lists.alioth.debian.org <http://lists.alioth.debian.org/> mailing lists is now underway. If you would
> like pkg-common-lisp-devel at lists.alioth.debian.org <mailto:pkg-common-lisp-devel at lists.alioth.debian.org>
> to be included in this process, to ensure that the list still works
> after the migration in late March/April, please let us know by replying
> to this email. Otherwise, the list will stop working at migration time
> and the archives will no longer be accessible.
>
> Feel free to also let us know if the list is no longer needed, so we can
> note that down too. Replies must be received by 15th March 2018.
>
> More information about the new service can be found here:
> <https://wiki.debian.org/Alioth/MailingListContinuation <https://wiki.debian.org/Alioth/MailingListContinuation>>
>
> Thanks,
> the alioth-lists migration team.
>
> [1] <https://lists.debian.org/debian-devel-announce/2018/01/msg00003.html <https://lists.debian.org/debian-devel-announce/2018/01/msg00003.html>>
I assume that we want to do this for the pkg-common-lisp-devel list, but not for the commits list?
Best regards, Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-common-lisp-devel/attachments/20180129/5d3d6424/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1003 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.alioth.debian.org/pipermail/pkg-common-lisp-devel/attachments/20180129/5d3d6424/attachment.sig>
Reply to: