id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	lang	patch	platform
1458	Don't add probed warnings to config information.	coke		"During configuration, all warnings that are successfully probed are entered into the parrot configuration. So if you built with gcc, you can run:

{{{
$ ./parrot_config -Wall
1
}}}

This seems like overkill, especially when:

{{{
./parrot_config ccwarn
}}}

seems sufficient. (ccwarn is empty in trunk, but what you'd expect in the rm_cflags branch.)

Feedback (esp. whether or not this constitutes a deprecation issue) welcome.
"	RFC	closed	normal		none	2.1.0	medium	fixed