This is the mail archive of the gdb-patches@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



At least one now :) There are a number of other solutions to this. Have you considered making the ARI mail contributors for certain
(low-false-positive) categories? Like, for instance, this one. The
gcc-regression mailing list has several scripts to pull the ChangeLog
entries since the last run and mail victims. It's extremely effective.

I find the GCC script anything but effective. I get spammed everytime I commit something to GCC - a very negative experience for an infrequent GCC committer. I've now been conditioned into ignoring that mail :-(


Contrast that to -Werror (yes ok, it isn't a requirement) and gdb_mbuild.sh. By encouraging their use we make it possible for people to address the problems _before_ they become an issue. That way the contributor and maintainer don't even need to discuss them. For something like the ARI to be mainlined, it would need to be integrated into the build process in a way that didn't leave the user confused (a standard build would have to be 100% warning free - something that at present is impossible to achieve).

enjoy,
Andrew



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