On Tue, 2010-09-14 at 16:16 -0400, Richard Ryniker wrote: > > Well, that's arguable. Many developers prefer apps to be 'chatty' and > > report things like this for informational purposes. It's a design > > choice, really. I encourage programs to generate copious output when they are in debug mode (such as in Rawhide or Alpha or when they detect serious internal problems or when explicitly requested) but other than that I encourage them to be quiet. Users should be encouraged to report burps in production systems, and if there's a lot of benign output which can't be distinguished from harmful output, the value of that is lost somewhat. I agree a downgrade to "warning" or "info" from "error" would help a lot. But the choice of channel is also important. I don't think programs should really be sending "info" level stuff to STDOUT; that's a channel fastidious users should be monitoring and reporting on (because I expect in normal operation there to be no output there). Just my $1.32. -B. -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
