Hallo Aric, I guess you use cvs nt as client AND server ...
Well, I do have the same problem. BTW take a closer look at http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt because it is a problem of the NT server. > [...] > I'm using ActivePerl 5.6.1 and CVS NT 1.11.1.1 (Build 27) and have tried > "print" and "print STDERR" statements: > > > # Be noisy if a problem number cannot be found > unless(scalar(@problems) > 0) { > print STDERR "LOGINFO: you should *really* provide a problem > number\n"; > print STDERR "LOGINFO: no problem event history will be > updated\n"; > } To get things to work on NT change your script message and add "E " print STDERR "E LOGINFO: no problem event history will be updated\n"; now the client should recognize the output as an error message from an script. (Use config of Perl to check, whether the script runs on NT or UNIX) > > with results that look consistently like: > > > D:\CVS\trunk\devscripts>cvs commit -m"test updated > loginfo_engineering.pl script" updateNameRefs.pl > Checking in updateNameRefs.pl; > c:/cvs/devscripts/updateNameRefs.pl,v <-- updateNameRefs.pl > new revision: 1.2; previous revision: 1.1 > done > cvs commit: warning: unrecognized response `LOGINFO: you should *really* > provide' from cvs server > cvs commit: warning: unrecognized response `LOGINFO: no problem event > history wi' from cvs server > > [...] The problem is that UNIX servers filter the output of scripts and put a "E " (stderr) or a "M " (stdout) at beginning of each new line; the NT server does not. You have to do this in your script or write the code for filtering script output on NT (see http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt). </Frank> _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
