From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27501 invoked by alias); 1 Jul 2004 05:04:27 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 27438 invoked from network); 1 Jul 2004 05:04:26 -0000 Received: from unknown (HELO cgf.cx) (66.30.22.40) by sourceware.org with SMTP; 1 Jul 2004 05:04:26 -0000 Received: by cgf.cx (Postfix, from userid 201) id CFFC64002DC; Thu, 1 Jul 2004 01:04:26 -0400 (EDT) Date: Thu, 01 Jul 2004 05:04:00 -0000 From: Christopher Faylor To: overseers@sourceware.org Subject: Do we really need the ezmlm mailing list archives? Message-ID: <20040701050426.GA27137@coe.casa.cgf.cx> Mail-Followup-To: overseers@sourceware.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-SW-Source: 2004-q3/txt/msg00000.txt.bz2 /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