From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] Put a copy of the TUHS mail archive into the Unix Archive?
Date: Sat, 25 Feb 2017 08:11:50 +1000 [thread overview]
Message-ID: <20170224221150.GB25938@minnie.tuhs.org> (raw)
In-Reply-To: <alpine.BSF.2.20.1702250836370.48029@aneurin.horsfall.org>
On Fri, 24 Feb 2017, Warren Toomey wrote:
> > Is it worth putting a copy of this mailing list into the Unix Archive?
On Sat, Feb 25, 2017 at 08:45:29AM +1100, Dave Horsfall wrote:
> It definitely ought to be archived, if you can obscure the email addresses
> whilst making them humanoid-readable. Damned spammers...
I've symlinked the mailman text archives in to the archive here:
http://www.tuhs.org/Archive/Documentation/TUHS/Mail_list/
Mailman does obfuscate the e-mail addresses somewhat.
Cheers, Warren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170225/bcdd2155/attachment.sig>
next prev parent reply other threads:[~2017-02-24 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 6:37 Warren Toomey
2017-02-24 21:45 ` Dave Horsfall
2017-02-24 21:57 ` Paul Ruizendaal
2017-02-24 22:11 ` Warren Toomey [this message]
2017-02-25 4:35 ` Random832
2017-02-25 2:10 ` Jason Stevens
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=20170224221150.GB25938@minnie.tuhs.org \
--to=wkt@tuhs.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).