From: Christopher Faylor <cgf-use-the-mailinglist-please@gcc.gnu.org>
To: gcc@gcc.gnu.org, overseers@sourceware.org
Subject: Re: Stability of pipermail ml archive URLs
Date: Thu, 7 May 2020 11:48:10 -0400 [thread overview]
Message-ID: <20200507154810.GA13473@cgf.cx> (raw)
In-Reply-To: <87r1vwxehp.fsf@euler.schwinge.homeip.net>
On Thu, May 07, 2020 at 11:48:18AM +0200, Thomas Schwinge wrote:
>On 2020-05-06T10:44:46-0400, "Frank Ch. Eigler via Gcc"
><gcc@gcc.gnu.org> wrote:
>>>Can pipermail provide stable URLs at all? We really need those, we
>>>reference those in commit messages, other mails, bugzilla etc.
>
>>It would be good to have another way of making permanent URLs for
>>individual messages in mailing list archives.
>
>Look up by Message-ID?
><http://mid.mail-archive.com/20200506141139.GJ2375@tucnak>, for
>example. See <https://en.wikipedia.org/wiki/Message-ID>, etc. The
>idea is that for all practical purposes, Message-IDs are "sufficiently
>unique". (Compare conceptually to the Git SHA-1 hashes.)
IMO, we're making way too big a deal out of this. The message archives
are changing because we are resequencing them. Mailman doesn't, AFAIK,
take it upon itself to randomly renumber them. fche and cgf have been
renumbering them when we remove spam.
If we stopped doing that there would be no issue.
When we were using ezmlm, I was careful not to remove message files when
dealing with spam. We haven't been that careful with mailman and, so,
we're seeing problems.
If we just changed the way that we deal with spam to keep the message
around but blank it out, we wouldn't have this problem.
In addition, when I was migrating the mail archives from ezmlm to mailman
I came across a number of cases where the same message-id was used in
two messages. Possibly it was someone just bouncing email or maybe
it was something else.
Maybe it's a corner case but we wouldn't have to worry about this at all
if we just used mailman's current numbering and didn't ever take it upon
ourselves to rescan the archives.
cgf
next prev parent reply other threads:[~2020-05-07 15:48 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 [this message]
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=20200507154810.GA13473@cgf.cx \
--to=cgf-use-the-mailinglist-please@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--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).