From: Christopher Faylor <cgf-use-the-mailinglist-please@gnu.org>
To: overseers@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>,
Tobias Burnus <burnus@net-b.de>
Subject: Re: GCC server – mailing archive's /current no longer working
Date: Sun, 8 Mar 2020 14:43:09 -0400 [thread overview]
Message-ID: <20200308184309.GA12383@cgf.cx> (raw)
In-Reply-To: <20200308174110.GA9565@cgf.cx>
On Sun, Mar 08, 2020 at 01:41:10PM -0400, Christopher Faylor via Overseers wrote:
>On Sun, Mar 08, 2020 at 12:27:48PM -0400, Christopher Faylor via Overseers wrote:
>>On Sun, Mar 08, 2020 at 11:13:45AM +0100, Tobias Burnus via Overseers wrote:
>>>how about simply redirecting "/ml/<name>/current" to
>>>"/pipermail/<name>"? This avoids the not-found issue and one ends up
>>>at the new mailing archive (albeit not for the current month, but
>>>that's way better than an error message).
>>
>>I experimented with that yesterday. It should work.
>
>I created the symlinks. They aren't quite the same as the old current
>since they point to the most recent folder with content rather than
>"this month's" folder. But, I think I actually would prefer that
>as a user since I rarely want to look at an empty folder.
I've just aliased /ml/ to pipermail so that, e.g.,
https://sourceware.org/ml/binutils
brings you to the new mailman archives.
Direct access of a url like:
https://sourceware.org/ml/binutils/2015-08/msg00084.html
still works.
I'll put it back to the way it was if there are problems but I hope
this is the best of both worlds.
cgf
prev parent reply other threads:[~2020-03-08 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 18:25 Tobias Burnus
2020-03-07 19:57 ` Frank Ch. Eigler
2020-03-07 19:59 ` Christopher Faylor
2020-03-08 10:13 ` Tobias Burnus
2020-03-08 16:27 ` Christopher Faylor
2020-03-08 17:41 ` Christopher Faylor
2020-03-08 18:43 ` Christopher Faylor [this message]
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=20200308184309.GA12383@cgf.cx \
--to=cgf-use-the-mailinglist-please@gnu.org \
--cc=burnus@net-b.de \
--cc=gerald@pfeifer.com \
--cc=overseers@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).