This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [commit] Deprecate remaining STREQ uses
- From: "Eli Zaretskii" <eliz at elta dot co dot il>
- To: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- Cc: cagney at gnu dot org, gdb at sources dot redhat dot com
- Date: Sun, 14 Dec 2003 20:11:34 +0200
- Subject: Re: [commit] Deprecate remaining STREQ uses
- References: <20031214160224.0FF864B412@berman.michael-chastain.com>
- Reply-to: Eli Zaretskii <eliz at elta dot co dot il>
> Date: Sun, 14 Dec 2003 11:02:24 -0500 (EST)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
>
> > 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?
It isn't 1-2 hours, unfortunately. More like a full day.
> 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.
No one seems to be stepping forward, and I haven't seen patches
submitted for quite some time, anyway. So it doesn't seem it will
make any difference.
That said, feel free to fire me.
> > Since your proposal for deprecating counts minor releases, would it
> > be enough to request a run for every such release?
>
> In my opinion, no.
Why not?
> > 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.
Again, why not?