> Install cvs in a different place than the version you are using. > > Make a script named cvs in the current location of cvs. That > script should check the cvs commands vs. valid users. If > everything is OK, then it should invoke the new cvs in the > new place with the arguments passed to it.
This is an interesting idea. > This won't protect you from truly malicious developers who > invoke cvs directly from the new location, but you probably > have already fired those people from your project. :-) None of the developers are malicious. The problem came up because on 3 separate occasions, a developer who is not very familiar with CVS somehow deleted 3 active branches. As to firing developers, that's out of my realm. I am just a lowly release engineer. :-) One person suggested an open source product called Sinis. http://sinis.sourceforge.net/ This product intrigues me. Has anyone on this list used Sinis? -Dave _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
