Howard, > Two questions really. We're using CVSNT 2.5.0.3 Scorpio (build 2704) > on a freebsd platform.
This was never an open source stable release (that was 2.5.03 2382, then we moved on to 2.5.04). Please test using 2.5.04. The 2.5.03 branch is for March hare Software internal use only. > 2) Is there any way to create a commit trigger of some sort, > that will > allow us to run a regex, or script to do some validation of > code, before > allowing a commit? We'd like to prevent developers from > committing code > that contains certain debug code. >From memory the file being committed is in the current directory during the execution of one of the triggers... Loginfo maybe? Generally this sort of thing doesn't work - it's the same as trying to prevent 'poor' commit messages, developers will find a way around it. Better to have a code review stage and if it is picked up then hit the developer with a 'big stick'. Regards, Arthur Barrett _______________________________________________ cvsnt mailing list [email protected] http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
