From: Christopher Faylor <cgf-use-the-mailinglist-please@gcc.gnu.org>
To: Jakub Jelinek <jakub@redhat.com>,
Overseers mailing list <overseers@sourceware.org>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Stability of pipermail ml archive URLs
Date: Wed, 6 May 2020 11:22:31 -0400 [thread overview]
Message-ID: <20200506152231.GA10446@cgf.cx> (raw)
In-Reply-To: <20200506141139.GJ2375@tucnak>
On Wed, May 06, 2020 at 04:11:39PM +0200, Jakub Jelinek wrote:
>Hi!
>
>Last week after sending status report mails to gcc mailing list,
>I've opened the web archive and copied the URLs of those status reports
>https://gcc.gnu.org/pipermail/gcc/2020-April/232267.html
>https://gcc.gnu.org/pipermail/gcc/2020-April/232268.html
>and checked them into gcc-wwwdocs git
>c3162d9e711d3e32935c17d1451c63839d702019 revision.
>But today people are complaining that those links don't work anymore
>and those mails have
>https://gcc.gnu.org/pipermail/gcc/2020-April/000504.html
>https://gcc.gnu.org/pipermail/gcc/2020-April/000505.html
>URLs instead.
>Martin Jambor also said he has posted a URL into the archive
>https://gcc.gnu.org/pipermail/gcc/2020-February/231851.html
>which is now instead
>https://gcc.gnu.org/pipermail/gcc/2020-February/232205.html
>Looking around, the last two months of gcc now have very small
>numbers, but e.g. on gcc-patches the mails have very high numbers like
>545238.html. Can pipermail provide stable URLs at all? We really
>need those, we reference those in commit messages, other mails, bugzilla
>etc.
I'll bet this is due to rebuilding the archive after removing spam.
Maybe we need to revisit how that's done.
cgf
next prev parent reply other threads:[~2020-05-06 15:22 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
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 [this message]
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=20200506152231.GA10446@cgf.cx \
--to=cgf-use-the-mailinglist-please@gcc.gnu.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).