From: Warner Losh <imp@bsdimp.com>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] TUHS web server has changed
Date: Thu, 5 May 2022 20:52:42 -0600 [thread overview]
Message-ID: <CANCZdfpfB0r2hj0Jr39cokv2ti76PpdQt1e5gyaKPT0QGLsChg@mail.gmail.com> (raw)
In-Reply-To: <515f9768-9508-5e07-9fb0-186744c2d461@spamtrap.tnetconsulting.net>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On Thu, May 5, 2022 at 8:41 PM Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
wrote:
> On 5/5/22 3:26 PM, Warren Toomey via TUHS wrote:
> > Yes, I plan on moving to Mailman 3.x. I'm hoping that I can import
> > the raw TUHS mbox (currently 130Mbytes). This, unfortunately,
> > will break the hyperlinks in the current mail archive
> > athttps://minnie.tuhs.org/pipermail/tuhs/
>
> Let's chat about this when the time comes.
>
> I strongly suspect there is a way to retain functionality for the old
> links, even if they are simply redirects to the new location. -- I have
> some ideas. }:-)
>
FreeBSD's archives were updated recently to not use mailman 3
despite the project using mailman 2 due to the link changing issue.
Warner
[-- Attachment #2: Type: text/html, Size: 1252 bytes --]
next prev parent reply other threads:[~2022-05-06 2:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 2:08 Warren Toomey via TUHS
2022-05-04 13:27 ` Clem Cole
2022-05-04 19:37 ` Mary Ann Horton
2022-05-05 0:52 ` Dave Horsfall
2022-05-05 5:43 ` Andy Kosela
2022-05-05 5:57 ` Grant Taylor via TUHS
2022-05-05 20:48 ` Dave Horsfall
2022-05-04 17:54 ` Grant Taylor via TUHS
2022-05-05 21:26 ` Warren Toomey via TUHS
2022-05-05 23:42 ` Gregg Levine
2022-05-06 2:38 ` Grant Taylor via TUHS
2022-05-06 2:52 ` Warner Losh [this message]
2022-05-06 4:32 ` Kenneth Goodwin
2022-05-07 16:13 ` Patrick Audley via TUHS
2022-05-09 16:12 ` Grant Taylor via TUHS
2022-05-09 17:55 ` Kenneth Goodwin
2022-05-09 19:22 ` Richard Salz
2022-05-09 19:57 ` Grant Taylor via TUHS
2022-05-09 18:37 ` Danil Smirnov
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=CANCZdfpfB0r2hj0Jr39cokv2ti76PpdQt1e5gyaKPT0QGLsChg@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=gtaylor@tnetconsulting.net \
--cc=tuhs@minnie.tuhs.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).