Hello, I'm here again to experiment with Scmbug. My problem is this: the log is too much verbose. I mean, since I'm not interested in Scmbug to monitor branching and tagging, I set the following options:
policies => label_name => enabled = 0 mail_notification => mail_on_label = 0 However, whenever I tag something in the CVS I receive from the CVS a lot of the following messages (one per file, I suppose): Scmbug notice: --------------------------------------------------------- Scmbug notice: Preparing for TAGGING Scmbug notice: Processing activity Scmbug notice: Submitting request Scmbug notice: Request submission was accepted This considerably slows down the tagging process (in certain cases we noticed that the time needed to tag our code base has doubled!). So I thought about lowering the log verbosity of the glue, thinking that those messages were at INFO level: however, looking at the configuration file and the glue code, I discovered that the default log level is already set to WARN and that those messages are actually logged as warnings. So, to alleviate my problem I could lower the log verbosity to ERROR, but I fear that in this way I will then lost messages about failed commits due to Scmbug polices not be satisfied. In fact, doing a quick dumb search on the code I find things like: ./Common.pm:522: $logger->warn( $error_string ); or ./Connection.pm:353: $logger->warn( "Request submission was $response" ); So, my question is: shouldn't the normal "request, processing, accepted" operations be logged as INFO, instead of WARNs? Otherwise, shouldn't the denied commits be logged as ERRORs? Thank you very much for any feedback on this. -- Mauro Molinari Software Designer & Developer E-mail: [email protected] _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
