From: Christopher Faylor <cgf-use-the-mailinglist-please@gcc.gnu.org>
To: Arseny Solokha <asolokha@gmx.com>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
Jakub Jelinek <jakub@redhat.com>,
Overseers mailing list <overseers@sourceware.org>,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: Stability of pipermail ml archive URLs
Date: Wed, 6 May 2020 11:24:31 -0400 [thread overview]
Message-ID: <20200506152431.GB10446@cgf.cx> (raw)
In-Reply-To: <c2842dae-585b-7aa5-22d0-5b3daad415d9@gmx.com>
On Wed, May 06, 2020 at 09:54:06PM +0700, Arseny Solokha wrote:
>may I also chime in with a related (to some extent), even though a separate
>issue? It seems URL rewriting rules designed to replace old-style
>
> https://gcc.gnu.org/ml/<list name>/current
>
>URLs pointing to monthly digests to current ones
>
> https://gcc.gnu.org/pipermail/<list name>/<year-month>/date.html#end
>
>broke with onset of May. I mean, if I type
>
> https://gcc.gnu.org/ml/gcc/current
>
>I still get
>
> https://gcc.gnu.org/pipermail/gcc/2020-April/date.html#end
>
>(note 2020-April) instead.
This is not related in any way.
I'll fix this. Apparently my cron job didn't fire.
cgf
next prev parent reply other threads:[~2020-05-06 15:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 14:11 Jakub Jelinek
2020-05-06 14:44 ` Frank Ch. Eigler
2020-05-06 14:54 ` Arseny Solokha
2020-05-06 15:24 ` Christopher Faylor [this message]
2020-05-06 14:55 ` Arseny Solokha
2020-05-07 9:48 ` Thomas Schwinge
2020-05-07 10:14 ` Frank Ch. Eigler
2020-05-07 15:54 ` Christopher Faylor
2020-05-07 17:56 ` Frank Ch. Eigler
2020-05-07 18:27 ` Christopher Faylor
2020-05-07 15:48 ` Christopher Faylor
2020-05-07 19:23 ` Segher Boessenkool
2020-05-07 20:28 ` Christopher Faylor
2020-05-06 15:22 ` Christopher Faylor
2020-05-06 16:04 ` Per Bothner
2020-05-06 20:55 ` Christopher Faylor
2020-05-06 21:06 ` Per Bothner
2020-05-07 3:55 ` 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=20200506152431.GB10446@cgf.cx \
--to=cgf-use-the-mailinglist-please@gcc.gnu.org \
--cc=asolokha@gmx.com \
--cc=fche@elastic.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=overseers@sourceware.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).