This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Close all [most] SPARC PRs?
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: cagney at gnu dot org, gdb at sources dot redhat dot com
- Date: Wed, 18 Feb 2004 16:47:40 -0500 (EST)
- Subject: Re: Close all [most] SPARC PRs?
> 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