From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <fche@elastic.org>
Received: from elastic.org (unknown [IPv6:2600:3c03::f03c:91ff:fe50:73f])
 by sourceware.org (Postfix) with ESMTPS id AC9A4386F44C
 for <overseers@sourceware.org>; Thu,  7 May 2020 10:14:58 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org AC9A4386F44C
Received: from vpn-home.elastic.org ([10.0.0.2] helo=elastic.org)
 by elastic.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
 (Exim 4.92.3) (envelope-from <fche@elastic.org>)
 id 1jWdYN-0006Z8-Qx; Thu, 07 May 2020 10:14:55 +0000
Received: from very.elastic.org ([192.168.1.1])
 by elastic.org with esmtp (Exim 4.92.3)
 (envelope-from <fche@elastic.org>)
 id 1jWdYN-000DeD-EA; Thu, 07 May 2020 06:14:55 -0400
Received: from fche by very.elastic.org with local (Exim 4.92.3)
 (envelope-from <fche@very.elastic.org>)
 id 1jWdYN-00EeW6-Cc; Thu, 07 May 2020 06:14:55 -0400
Date: Thu, 7 May 2020 06:14:55 -0400
From: "Frank Ch. Eigler" <fche@elastic.org>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: Jakub Jelinek <jakub@redhat.com>, overseers@sourceware.org, gcc@gcc.gnu.org
Subject: Re: Stability of pipermail ml archive URLs
Message-ID: <20200507101455.GC2466959@elastic.org>
References: <20200506141139.GJ2375@tucnak>
 <20200506144446.GB2466959@elastic.org>
 <87r1vwxehp.fsf@euler.schwinge.homeip.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87r1vwxehp.fsf@euler.schwinge.homeip.net>
X-Sender-Verification: ""
X-Sender-Verification: ""
X-Spam-Status: No, score=-105.4 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_PASS, SPF_PASS, TXREP,
 USER_IN_WHITELIST autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: overseers@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Overseers mailing list <overseers.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/overseers>,
 <mailto:overseers-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/overseers/>
List-Post: <mailto:overseers@sourceware.org>
List-Help: <mailto:overseers-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/overseers>,
 <mailto:overseers-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Thu, 07 May 2020 10:14:59 -0000

Hi -

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

- FChE