From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15967 invoked by alias); 21 May 2003 21:06:56 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 15935 invoked from network); 21 May 2003 21:06:55 -0000 Received: from unknown (HELO dberlin.org) (69.3.5.6) by sources.redhat.com with SMTP; 21 May 2003 21:06:55 -0000 Received: from [192.168.1.3] (account dberlin HELO dberlin.org) by dberlin.org (CommuniGate Pro SMTP 4.1b6) with ESMTP-TLS id 4052068 for gcc@gcc.gnu.org; Wed, 21 May 2003 17:06:55 -0400 Date: Wed, 21 May 2003 21:07:00 -0000 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: At the request of those drowing in gcc-bugs email From: Daniel Berlin To: gcc@gcc.gnu.org Content-Transfer-Encoding: 7bit Message-Id: <2645E0FC-8BD0-11D7-AF07-000A95A34564@dberlin.org> X-SW-Source: 2003-05/txt/msg01960.txt.bz2 I have changed gcc-bugs's email preferences so it only gets mail about the following: "New Comments are added" "Priority, status, severity, and/or milestone changes" "The bug is resolved or verified " "The bug is in the unconfirmed state" The following will not cause gcc-bugs to receive mail: "New Attachments are added" "Keywords field changes" "CC field changes" "Any field not mentioned above changes" If we want to make decisions that we want certain types of mail to go to certain lists or something, we can. --Dan