From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 356 invoked by alias); 8 Jan 2003 19:39:57 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 32383 invoked from network); 8 Jan 2003 19:38:25 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by 209.249.29.67 with SMTP; 8 Jan 2003 19:38:23 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id h08Jc6U17038; Wed, 8 Jan 2003 13:38:06 -0600 Date: Wed, 08 Jan 2003 19:39:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200301081938.h08Jc6U17038@duracef.shout.net> To: ac131313@redhat.com Subject: Re: [patch] README: remove references to deleted remote-*.c Cc: gdb-patches@sources.redhat.com X-SW-Source: 2003-01/txt/msg00333.txt.bz2 Andrew C writes: > Looks like I've been un-subscribed. Ah, the power of randomness. :) > If it really is still receiving much spam then that subscribe wouldn't > help (and could possibly confuse things). sware would bounce a bug > submittion that @gnu.org had accepted, or sware would just end up full > of spam reports. bug-gdb is a mailman mailing list. I would like to become a list administrator and set it up to moderate the submissions, together with a whitelist. Then there would be zero spam, so it would be safe to subscribe gdb-gnats to it. Or we could find some other way to pull the reports in. Or we could just acknowledge that e-mail bug reports aren't collected into our database (which I think is crummy). Michael C