From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14127 invoked by alias); 16 Mar 2002 15:42:48 -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 14075 invoked from network); 16 Mar 2002 15:42:45 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.135.44) by sources.redhat.com with SMTP; 16 Mar 2002 15:42:45 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 553A23EBE; Sat, 16 Mar 2002 10:42:43 -0500 (EST) Message-ID: <3C9367F3.3060708@cygnus.com> Date: Sat, 16 Mar 2002 07:42:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.8) Gecko/20020210 X-Accept-Language: en-us MIME-Version: 1.0 To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: High priority PRs References: <3C92825D.7020904@cygnus.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-03/txt/msg00149.txt.bz2 > I'm currently going through the PR database identifying a few PRs, making them High, the rest being put back to medium. > > This idea is stolen straight from GCC. A High Priority PR identifies something that is (hopefully) going to be fixed in the next release > > The ones I'm identifying (HP/UX, AIX, True64) are config/build problems where a patch has been submitted. (Hi Alex :-) Done. See attached. They'll either get fixed or listed as PROBLEMS. Anyone want to attack the debug info regressions? Andrew http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=submit%20query&database=gdb&category=gdb&severity=all&priority=high&responsible=all&submitter_id=net&state=all&ignoreclosed=Ignore%20Closed&class=all&synopsis=&multitext=&columns=category&columns=state&columns=priority&columns=responsible&columns=synopsis&displaydate=Display%20Current%20Date&sortby=Responsible&queryname=High%20%28for%20releases%29