From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: October 2023 Archives
Date: Fri, 20 Oct 2023 09:08:11 +0100 [thread overview]
Message-ID: <7B4BD4CD-2AE6-44C7-8A70-F02C6188F98D@ipfire.org> (raw)
In-Reply-To: <1b113e6365b19fe99ef1c50eb7592f27bb9dab93.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
Hello everyone,
Yes, this is correct.
Peter updated Mailman to Mailman 3 which changes a lot of things.
However, there should have been redirects from the old URLs to the new ones and the old archives should have been taken down.
I have opened a ticket for him to take care of this:
https://bugzilla.ipfire.org/show_bug.cgi?id=13398
Thank you for raising this.
Best,
-Michael
> On 20 Oct 2023, at 07:49, ummeegge <ummeegge(a)ipfire.org> wrote:
>
> It seems that a new version (update to mailman3) has been introduced --
>>
> https://lists.ipfire.org/mailman3/hyperkitty/list/development(a)lists.ipfire.org/
> or via
> https://lists.ipfire.org
> and the URL has been changed.
>
> Best,
>
> Erik
>
>
> Am Donnerstag, dem 19.10.2023 um 21:10 -0500 schrieb jon:
>> I see the same thing. Last update was Oct 1.
>>
>>
>>
>>
>>
>>
>> Jon Murphy
>> jon.murphy(a)ipfire.org
>>
>>
>>
>>> On Oct 19, 2023, at 5:57 PM, Charles Brown <cab_77573(a)yahoo.com>
>>> wrote:
>>>
>>> Is it just me? I see no updates to "October 2023 Archives" past
>>> Oct 1st.
>>>
>>>
>>> https://lists.ipfire.org/pipermail/development/2023-October/date.ht
>>> ml
>>>
>>> .
>>>
>>>
>>
>
next prev parent reply other threads:[~2023-10-20 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43888844-2084-4277-B8F6-978A91E71448@ipfire.org>
2023-10-20 6:49 ` ummeegge
2023-10-20 8:08 ` Michael Tremer [this message]
[not found] <860BE64E-B3EF-4AF7-AE7C-A0EBA38E36D3@ipfire.org>
2023-10-30 10:08 ` Michael Tremer
[not found] <1e120b3e-b10b-4b73-903d-187bca7253f5.ref@yahoo.com>
2023-10-19 22:57 ` Charles Brown
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=7B4BD4CD-2AE6-44C7-8A70-F02C6188F98D@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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