From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21593 invoked by alias); 5 Mar 2005 17:41:08 -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 21562 invoked by uid 48); 5 Mar 2005 17:41:03 -0000 Date: Wed, 16 Mar 2005 17:56:00 -0000 From: "jsm28 at gcc dot gnu dot org" To: overseers@gcc.gnu.org Message-ID: <20050305174100.20336.jsm28@gcc.gnu.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug web/20336] New: gaps in list archives X-Bugzilla-Reason: AssignedTo X-SW-Source: 2005-q1/txt/msg00310.txt.bz2 The online list archives for February, both web and ftp, have gaps around the time of the system failure (i.e., from last backup to when the system went down) which need filling in from the qmail archives or any other archives if there are problems with those. Note that the ftp mbox archives include headers with the qmail message numbers so the exact missing messages there can be identified. Note that MHonarc is supposed to detect duplicates using message-id so it should be safe to feed in more messages than just the missing ones. Note that for some archives the message numbers in the presently online index go backwards, e.g. in the gcc-bugs archives msg00244.html to msg00284 from after the failure overwrote those messages from before the failure, although the index pages link to those messages with both old and new subject headings. This applies to gcc-bugs, libstdc++, java, java-patches (quarterly archive), libstdc++-cvs (quarterly), java-prs (quarterly) at least. (Issues may also apply for non-GCC lists on the site, though this isn't strictly within the scope of a GCC bug report.) -- Summary: gaps in list archives Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: web AssignedTo: overseers at gcc dot gnu dot org ReportedBy: jsm28 at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20336 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.