all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: mailing list archives
Date: Thu, 06 Jun 2013 18:26:06 +0900	[thread overview]
Message-ID: <87sj0va8up.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <CAAF+z6G8+iAT2FSwMRvVXTP2p2HJrYZWMXh9qeXXvDx1QAstew@mail.gmail.com>

Xue Fuqiao writes:
 > On Thu, Jun 6, 2013 at 5:49 AM, Glenn Morris <rgm@gnu.org> wrote:
 > >
 > > It's just how Mailman archives work, and no, no-one here can do
 > > anything about it.
 > 
 > Agreed.  I'm not familiar with Mailman, but I think this topic should be
 > discussed here: https://bugs.launchpad.net/mailman

Please, don't waste our time and yours; the bug will just be closed
wontfix.  The issues with the stock archiver Pipermail are well-known,
there are plenty of good alternatives if you can't live with them now
(it's easy to hook up MHonArc, mail-archive.com, or gmane), and
Pipermail is end-of-life[1] (as is all of Mailman 2).  Only security
and easy-fix issues go into Mailman 2 nowadays.  Threading in
Pipermail is neither.

Mailman 3 will have a completely different stock archive manager (in
fact, a separate project currently called HyperKitty).  We haven't yet
decided if it will be bundled, but I think probably it will be.

For more info (don't ask me, it's not my baby):
    https://fedorahosted.org/hyperkitty/
    https://hyperkitty.readthedocs.org/
    https://github.com/hyperkitty

Footnotes: 
[1]  As much as any free software can be EOLed, of course.




  reply	other threads:[~2013-06-06  9:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 15:56 mailing list archives Drew Adams
2013-06-05 21:49 ` Glenn Morris
2013-06-05 23:19   ` Xue Fuqiao
2013-06-06  9:26     ` Stephen J. Turnbull [this message]
2013-06-06 13:50       ` Xue Fuqiao

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=87sj0va8up.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=emacs-devel@gnu.org \
    --cc=xfq.free@gmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.