From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6450 invoked by alias); 23 Jun 2004 19:50:54 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6436 invoked from network); 23 Jun 2004 19:50:53 -0000 Received: from unknown (HELO tisch.mail.mindspring.net) (207.69.200.157) by sourceware.org with SMTP; 23 Jun 2004 19:50:53 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by tisch.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1BdDlW-0005jP-00; Wed, 23 Jun 2004 15:50:38 -0400 Received: by berman.michael-chastain.com (Postfix, from userid 502) id E8A974B104; Wed, 23 Jun 2004 15:51:09 -0400 (EDT) To: cagney@gnu.org, jimb@redhat.com Subject: Re: Technical criteria for retaining symbol readers Cc: gdb@sources.redhat.com, mec.gnu@mindspring.com Message-Id: <20040623195109.E8A974B104@berman.michael-chastain.com> Date: Wed, 23 Jun 2004 19:50:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-06/txt/msg00242.txt.bz2 jimb> I'd also like to have some kind of requirement for testability. I would, too. My preference would be that we look at gdb-testers@ and if there are no test results for feature X for the past N years, that counts against keeping feature X. gcc uses that as one factor in deciding whether to obsolete stuff. As far as Andrew's original proposal goes, it's okay with me to set up some criteria for dropping formats. Michael C