From: marcus-sup@quintic.co.uk (Marcus Williams)
Subject: [sup-talk] sup-talk emails in mbox format?
Date: Tue, 23 Oct 2007 16:46:05 +0100 [thread overview]
Message-ID: <471E173D.5000302@quintic.co.uk> (raw)
In-Reply-To: <00f6cdb300007d75@IMSS-WIN>
On 23/10/2007 vasudeva wrote:
> Anyone have the full sup-talk mailing list in mbox format, so I can get
> it into sup for easy reference? Google's being a pain in the ass about
> giving me what I want, and the mailman interface only serves up the
> archive as plaintext files.
Whilst they are plain text, they are actually stripped mbox's. Sup can
index them (thats how I've put mine into sup anyway), just treat old
archives as "unusual".
The only problem with this is that mailman has stripped old email
addresses out of the archives so you dont get to see who wrote what, so
a mbox with all of this info would still be useful (so I guess thats a
me too! post)
Marcus
next parent reply other threads:[~2007-10-23 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00f6cdb300007d75@IMSS-WIN>
2007-10-23 15:46 ` Marcus Williams [this message]
2007-10-23 15:50 ` Alexander Panek
2007-10-23 13:42 vasudeva
2007-10-23 16:59 ` Christopher Warrington
2007-10-26 23:21 ` William Morgan
2007-10-27 15:25 ` vasudeva
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=471E173D.5000302@quintic.co.uk \
--to=marcus-sup@quintic.co.uk \
/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