From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15189 invoked by alias); 18 Feb 2004 21:48: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 15180 invoked from network); 18 Feb 2004 21:48:46 -0000 Received: from unknown (HELO blount.mail.mindspring.net) (207.69.200.226) by sources.redhat.com with SMTP; 18 Feb 2004 21:48:46 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by blount.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1AtZXs-0007Rs-00; Wed, 18 Feb 2004 16:47:52 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id D8E584B367; Wed, 18 Feb 2004 16:47:40 -0500 (EST) To: cagney@gnu.org, gdb@sources.redhat.com Subject: Re: Close all [most] SPARC PRs? Message-Id: <20040218214740.D8E584B367@berman.michael-chastain.com> Date: Wed, 18 Feb 2004 21:48:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-02/txt/msg00233.txt.bz2 > Given that the SPARC code has been effectively rewritten, should all the > old sparc PRs be closed? I think so. I like to reply to such PR's like this: Hello, I'm working through old gdb PR's and I've come to your PR gdb/NNNN, filed in December 1998. The Sparc code has recently been rewritten and many bugs were fixed. I tried your test case (or something similar to your test case) and it works for me. (Or leave this line out if you just can't). Can you please try a CVS version of gdb or a recent snapshot of gdb and let me know if it works for you. Michael C GDB QA Guy Attach that message in a change from "open" -> "feedback". Wait 30 days. About 80% of cases, nothing happens for 30 days. Then close the PR, with another little note: "I haven't heard anything for 30 days. I am closing the PR. If you have problems with a more recent version of gdb, please file another PR." About 15% of cases, the original submitter writes back sooner and confirms that the original bug is closed. Then close the PR. About 5% of cases, the original submitter says something which indicates that we shouldn't close the PR. Mark K already did a 30-day routine on a bunch of Solaris PR's, and the 30 days ran out, and he closed the PR's. Anyways, that's how I like to do it. Michael C