public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Tobias Burnus <burnus@net-b.de>
To: overseers@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: GCC server – mailing archive's /current no longer working
Date: Sun, 8 Mar 2020 11:13:45 +0100	[thread overview]
Message-ID: <aee4af7e-9c8c-6867-58fe-042e3f66d460@net-b.de> (raw)
In-Reply-To: <20200307195928.GA9718@cgf.cx>

Hi,

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).

Cheers,

Tobias

On 3/7/20 8:59 PM, Christopher Faylor wrote:
> On Sat, Mar 07, 2020 at 07:25:44PM +0100, Tobias Burnus wrote:
>> I don't know whether this due to the move to the new server, but the
>> "current" links to the current month does no longer work:
>>
>> https://gcc.gnu.org/ml/gcc-patches/current shows not found but should
>> re-direct (this month) to https://gcc.gnu.org/ml/gcc-patches/2020-03/
>> as always working and as documented under https://gcc.gnu.org/ml/
> We're using mailman now so the "current" link no longer works.  The /ml/
> directory is currently only for legacy mailing lists.  Mailman puts the
> archives in, e.g., https://gcc.gnu.org/pipermail/gcc-patches/ .
>
> I'm thinking about ways to merge the old and new archives but, for now,
> you must use the /pipermail/ link to access archives in the new
> sourceware.
>
> cgf
>

  reply	other threads:[~2020-03-08 10:13 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 [this message]
2020-03-08 16:27     ` Christopher Faylor
2020-03-08 17:41       ` Christopher Faylor
2020-03-08 18:43         ` Christopher Faylor

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=aee4af7e-9c8c-6867-58fe-042e3f66d460@net-b.de \
    --to=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).