Re: Close all [most] SPARC PRs?

Re: Close all [most] SPARC PRs?

[Michael Elizabeth Chastain]

Andrew Cagney writes:
ac> I don't think it should put too much emphasis on this:
mec>   I tried your test case (or something similar to your test case)
mec>   and it works for me. 

Well, one could say "I was unable to try your test case" or
"could I ask you to try it again with a recent gdb?".

Michael C

Re: Close all [most] SPARC PRs?

[Andrew Cagney]

> Andrew Cagney writes:
> ac> I don't think it should put too much emphasis on this:
> mec>   I tried your test case (or something similar to your test case)
> mec>   and it works for me. 
> 
> Well, one could say "I was unable to try your test case" or
> "could I ask you to try it again with a recent gdb?".

The latter.  If the're active and respond then there is a good chance 
that the problem will get closed/fixed.

Andrew

Re: Close all [most] SPARC PRs?

[Eli Zaretskii]

> Date: Fri, 20 Feb 2004 11:55:06 -0500
> From: Andrew Cagney <cagney@gnu.org>
> 
> (<eli>doco?</eli> :-)

What doco?

Re: Close all [most] SPARC PRs?

[Andrew Cagney]

>>Date: Wed, 18 Feb 2004 16:47:40 -0500 (EST)
>>> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
>>> 
>>> 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.
> 
> 
> I really like this procedure.  Blindly closing the PRs should not be
> our first choice if we can do better, and what Michael suggests _is_,
> IMHO, better.

I don't think it should put too much emphasis on this:

> I tried your test case (or something similar to your test case)
>   and it works for me. 

(<eli>doco?</eli> :-)

Andrew

Re: Close all [most] SPARC PRs?

[Eli Zaretskii]

> Date: Wed, 18 Feb 2004 16:47:40 -0500 (EST)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
> 
> 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.

I really like this procedure.  Blindly closing the PRs should not be
our first choice if we can do better, and what Michael suggests _is_,
IMHO, better.

Re: Close all [most] SPARC PRs?

[Michael Elizabeth Chastain]

> 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

Close all [most] SPARC PRs?

[Andrew Cagney]

Hello,

Given that the SPARC code has been effectively rewritten, should all the 
old sparc PRs be closed?  I think so.

Andrew