From: Christopher Faylor <me@cgf.cx>
To: overseers@sourceware.org
Subject: Do we really need the ezmlm mailing list archives?
Date: Thu, 01 Jul 2004 05:04:00 -0000 [thread overview]
Message-ID: <20040701050426.GA27137@coe.casa.cgf.cx> (raw)
/sourceware/qmail is filling up and we'll either have to extend the
partition or delete archives. I am wondering why we are going to the
effort of storing the ezmlm archives. We now store the archives in four
different places -- we store them as html for searching, we store most
of them as raw text for downloading, we store them as ftpable archives,
and we store them in the ezmlm directories where people can (rather
inconveniently) download them via ezmlm commands.
Given how often I suspect people try to download things using ezmlm
I wonder if we should forego archving like this from now on. It
will reclaim quite a bit of disk space, if we decide that we don't
need to allow people to download archives using ezmlm.
cgf
next reply other threads:[~2004-07-01 5:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 5:04 Christopher Faylor [this message]
2004-07-01 12:29 ` Gerald Pfeifer
2004-07-01 12:38 ` Jason Molenda
2004-07-01 14:28 ` Christopher Faylor
2004-07-01 18:04 ` Christopher Faylor
2004-07-01 14:30 ` Christopher Faylor
2004-07-01 12:35 ` Joseph S. Myers
2004-07-01 14:20 ` Jeffrey A Law
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=20040701050426.GA27137@coe.casa.cgf.cx \
--to=me@cgf.cx \
--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).