This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [commit] Deprecate remaining STREQ uses


Hi Eli,

> However, running the script once a month (on the then-latest snapshot,
> I presume) is not something that I can afford, and I don't see anyone
> else stepping forward to do that for me.

If you can't commit 1-2 hours per month to test djgpp gdb, how are you
going to respond to bug reports and patches?  What's going to happen
when it bit rots and stops building?

I think you should reconsider whether you have the resources to be a
maintainer for djgpp gdb.

> Since your proposal for deprecating counts minor releases, would it
> be enough to request a run for every such release?

In my opinion, no.

> Isn't it better to start deprecating only if we know that some code
> specific to a platform is broken by a certain change to GDB?

Again, in my opinion, no.

The official gdb definition of "supported" is "gdb builds and break main;
run" works.  Personally, I think that's lame.  However, what we have
right now is a situation where we aren't even working to that standard.

Michael C


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]