From: Thomas Schwinge <thomas@codesourcery.com>
To: "Frank Ch. Eigler" <fche@elastic.org>,
Jakub Jelinek <jakub@redhat.com>, <overseers@sourceware.org>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Stability of pipermail ml archive URLs
Date: Thu, 7 May 2020 11:48:18 +0200 [thread overview]
Message-ID: <87r1vwxehp.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <20200506144446.GB2466959@elastic.org>
Hi!
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.)
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".
(That's one reason why when posting such links I used to use Gmane's
Message-ID lookup, now using The Mail Archive's. The other reason is
that compared to Mailman's Pipermail these services don't artificially
break discussion threads at month boundaries.)
By the way, the public-inbox software
(<https://public-inbox.org/README.html>), as recently mentioned in a
different thread discussing deficiencies of Mailman's Pipermail, also
does support this:
<https://public-inbox.org/libc-alpha/129c8494-bfd0-87f0-ddb5-e56f6d4a6e0c@gotplt.org>
(random example). (I have not yet really looked into that software
myself, but from the little I read about it, it seems conceptually
simple, "easy", good.)
If there's sufficient interest (users) and commitment (overseers), we
could install this on sourceware, in addition to what we've currently
got?
Grüße
Thomas
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter
next prev parent reply other threads:[~2020-05-07 9: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 [this message]
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=87r1vwxehp.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=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).