From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Mailing lists and news archiving
Date: Sat, 05 Jan 2002 20:36:40 +0100 [thread overview]
Message-ID: <m33d1k37zr.fsf@quimbies.gnus.org> (raw)
I'm going through old mail, and mailing lists I'm subscribed to, but
haven't read in a while. And I'm struck by how much of our collective
knowledge is on these mailing lists, and how ephemeral they are. Some
of them are archived here and there, but the archives go away or move
or don't work.
News, on the other hand, don't really go away if you don't run
expiry. If more people are interested mirroring, you just start
feeding. Or mirror using other means.
So I'm wondering whether I should start setting up mail-to-news
gateways for all the mailing lists I'm subscribed to. And, of course,
any other mailing lists that people would want me to store.
Does this seem like an OK idea?
The mailing lists I would gateway would be, at least:
XEmacs Beta <xemacs-beta@xemacs.org>
Emacs Custom <emacs-custom@sunsite.dk>
XEmacs Mule <xemacs-mule@xemacs.org>
Emacs Development <emacs-devel@gnu.org>
Linux Kernel <linux-kernel@vger.kernel.org>
Linux USB <linux-usb-devel@lists.sourceforge.net>
Is this a good idea? A bad idea? And what would the hierarchy be
called?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next reply other threads:[~2002-01-05 19:36 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 19:36 Lars Magne Ingebrigtsen [this message]
2002-01-05 19:57 ` Lars Magne Ingebrigtsen
2002-01-05 21:00 ` news
2002-01-05 21:06 ` news
2002-01-05 21:36 ` Lars Magne Ingebrigtsen
2002-01-05 22:12 ` news
2002-01-06 7:13 ` Steinar Bang
2002-01-06 8:57 ` Lars Magne Ingebrigtsen
2002-01-06 14:13 ` Kai Großjohann
2002-01-19 20:01 ` Lars Magne Ingebrigtsen
2002-01-20 17:27 ` Kai Großjohann
2002-01-20 17:34 ` Lars Magne Ingebrigtsen
2002-01-20 17:38 ` Lars Magne Ingebrigtsen
2002-01-20 17:55 ` Lars Magne Ingebrigtsen
2002-01-20 21:33 ` Björn Torkelsson
2002-01-20 21:37 ` Lars Magne Ingebrigtsen
2002-01-22 1:23 ` Steve Youngs
2002-01-22 1:37 ` Lars Magne Ingebrigtsen
2002-01-22 2:23 ` Steve Youngs
2002-01-20 20:48 ` Steve Youngs
2002-01-20 17:35 ` Simon Josefsson
2002-01-06 2:09 ` Russ Allbery
2002-01-06 9:07 ` Lars Magne Ingebrigtsen
2002-01-08 12:52 ` Per Abrahamsen
2002-01-09 3:06 ` Russ Allbery
2002-01-09 10:55 ` Per Abrahamsen
2002-01-09 11:45 ` Russ Allbery
2002-01-19 20:04 ` Lars Magne Ingebrigtsen
2002-01-20 5:06 ` Karl Eichwalder
2002-01-05 22:47 ` Harry Putnam
2002-01-06 9:05 ` Lars Magne Ingebrigtsen
2002-01-06 9:52 ` Harry Putnam
2002-01-06 10:10 ` Lars Magne Ingebrigtsen
2002-01-06 10:23 ` Harry Putnam
2002-01-06 10:24 ` Lars Magne Ingebrigtsen
2002-01-06 10:40 ` Lars Magne Ingebrigtsen
2002-01-06 10:49 ` Lars Magne Ingebrigtsen
2002-01-06 11:25 ` Lars Magne Ingebrigtsen
2002-01-06 14:51 ` Karl Kleinpaste
2002-01-07 11:49 ` Colin Marquardt
2002-01-07 12:06 ` Lars Magne Ingebrigtsen
2002-01-07 18:13 ` Steinar Bang
2002-01-07 19:38 ` Lars Magne Ingebrigtsen
2002-01-08 9:06 ` Colin Marquardt
2002-01-06 12:42 ` Steinar Bang
2002-01-06 6:58 ` Steinar Bang
2002-01-06 9:13 ` Lars Magne Ingebrigtsen
2002-01-06 13:14 ` Frank Schmitt
2002-01-06 14:01 ` Florian Weimer
2002-01-06 15:38 ` Martin Thornquist
2002-01-07 7:58 ` Lars Magne Ingebrigtsen
2002-01-07 8:46 ` Simon Josefsson
2002-01-08 10:31 ` Fabien Penso
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=m33d1k37zr.fsf@quimbies.gnus.org \
--to=larsi@gnus.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 NNTP newsgroup(s).