public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@elastic.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 10:44:46 -0400	[thread overview]
Message-ID: <20200506144446.GB2466959@elastic.org> (raw)
In-Reply-To: <20200506141139.GJ2375@tucnak>

Hi -

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

Argh, that is a problem, sorry.  We get mailman to regenerate web
archives for example in the case of spam that has gone through.  Our
recipe has been to delete the spam from the apropriate .mbox, but this
does renumber things.

The big vs. little numbers are probably an accidental function of
whether the email .mbox files were processed chronologically or not.
I'll tweak the mrefresh script to make sure it's chronological; that
should avoid gross jumps like that.  I believe gcc-patches just wasn't
regenerated for spam removal whereas others have.  There should not be
gross jumps in the future, except we'll have to regenerate everything
one more time. :-(

Small jumps though --- darn, we'd have to do something else with spam
in the mbox, maybe replace it somehow in situ with something else.  Or
catch it so quickly that subsequent URLs aren't archived anywhere
important.

It would be good to have another way of making permanent URLs for
individual messages in mailing list archives.

- FChE

  reply	other threads:[~2020-05-06 14:44 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 [this message]
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
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=20200506144446.GB2466959@elastic.org \
    --to=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).