This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [commit] Deprecate remaining STREQ uses
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: eliz at elta dot co dot il
- Cc: cagney at gnu dot org, gdb at sources dot redhat dot com
- Date: Mon, 15 Dec 2003 01:22:30 -0500 (EST)
- Subject: Re: [commit] Deprecate remaining STREQ uses
eli> Since your proposal for deprecating counts minor releases, would it
eli> be enough to request a run for every such release?
mec> In my opinion, no.
eli> Why not?
Known regressions still go months before fixing. And I don't mean
"months until the elusive bug can be duplicate"; I mean "months after I
file a PR with a simple test case and a pointer to the exact patch where
gdb broke".
Then consider how much worse this would be if I did one run per release
instead of several runs per week.
eli> Isn't it better to start deprecating only if we know that some code
eli> specific to a platform is broken by a certain change to GDB?
mec> Again, in my opinion, no.
eli> Again, why not?
Because nobody knows what change is going to break what platform.
And I'm getting tired of this conversation because I don't see any
constructive action coming out of it. I'm going to continue my
aggressive QA campaign. When I bump into someone, such as I've bumped
into David Anglin or you, my attitude is going to be "well, what can you
contribute to support the platform?"
Michael C