Well, what if we made some sort of parser... I'm sure there must be a way to generate enough platform output (after building) to identify enough platforms (while not overkilling in statistsics) and then comparing which tests fail and how... I couldn't promise to do this immediately (not making enough income and scrambling to get contracts has been eating my time lately :-( ), but I'd certainly be interested longer term... Maybe I can give a lecture on it at YAPC::Israel::2004 - I've been scratching my head for a good topic to talk about anyway ;-)
Not to offend anybody, but people are coming up with good ideas, volunteering to stand behind them, tend to disappear the moment we finish polishing the details, after spending so many hours discussing the thing... This just what happens. So may I suggest that we just keep things the way they are (no automatic bug-reports)? We make it easier for users to know what to do in case of errors (the topic of this thread) and we will be just fine.
It sure thing would be nice not to have to reply with the usual 'please resubmit the bug report using the followinig guidelines' reply, but I don't mind doing that. It's really the user that suffers from not knowing how to submit a proper bug report, because it takes longer for the problem to get fixed and user being able to start using mod_perl.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
