public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: overseers@sourceware.org, gcc@gcc.gnu.org
Subject: Re: Stability of pipermail ml archive URLs
Date: Thu, 7 May 2020 11:54:42 -0400	[thread overview]
Message-ID: <20200507155442.GB13473@cgf.cx> (raw)
In-Reply-To: <20200507101455.GC2466959@elastic.org>

On Thu, May 07, 2020 at 06:14:55AM -0400, Frank Ch. Eigler wrote:
>>Such a service is not currently available on sourceware, but it'd be
>>possible to implement: as messages come in, you'd build a database
>>mapping from the Message-ID header to "current Mailman's Pipermail
>>URL".
>
>I was thinking we might be able to trick pipermail (the web archiver
>component) to simply name the message web urls after some function of
>the message-id instead of the sequence number.  Will give this a try
>very shortly.

I just want to go on record as saying that I think this is a bad idea.
We can fix this problem simply without redesigning pipermail.  The
problem that we're seeing is caused by a script that I wrote to migrate
ezmlm to mailman.  The fix for the problem is "Don't run that script".

But, if we are going to make this level of change to pipermail we might
as well go wild and just implement all of the other things that people
want and forget about our supposed desire to use "supported" software.
Changing pipermail to use message-id's rather than sequence numbers
negates the argument that we want to be standard since we likely won't
be able to get this change in upstream.  I doubt that mailman2
developers will want to consider this major a change in a product that
is supposedly close to EOL.

cgf


  reply	other threads:[~2020-05-07 15:54 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 [this message]
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=20200507155442.GB13473@cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.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).