From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: gcc@gcc.gnu.org, overseers@sourceware.org
Subject: Re: Stability of pipermail ml archive URLs
Date: Thu, 7 May 2020 16:28:39 -0400 [thread overview]
Message-ID: <20200507202839.GA15871@cgf.cx> (raw)
In-Reply-To: <20200507192330.GE31009@gate.crashing.org>
On Thu, May 07, 2020 at 02:23:30PM -0500, Segher Boessenkool wrote:
>On Thu, May 07, 2020 at 11:48:18AM +0200, Thomas Schwinge wrote:
>>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?
>
>I would very much like this. *All* of the problems with the current
>mail archive, as well as all of the problems with the one we had
>before, do not exist with public-inbox.
>
>(It probably has problems all of its own, of course ;-) )
It's been suggested many times both before we rolled out the new
sourceware and after.
I'm not a real fan of the interface but at least it's being supported.
It's just not supported in RHEL 8 right now, as far as I know.
To reiterate our current philosophy: We're trying to use supported
software on sourceware and not have to roll our own and worry about
keeping track of upstream fixes and security issues.
next prev parent reply other threads:[~2020-05-07 20:28 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
2020-05-07 19:23 ` Segher Boessenkool
2020-05-07 20:28 ` Christopher Faylor [this message]
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=20200507202839.GA15871@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).