At 12:05 PM 3/22/2002 , David Everly wrote: >Is there some technique I can use to prevent my developers from >directly altering the cvs repository and force them to use cvs >commands instead?
If developers don't have direct access to the repository (they can't log onto the repository machine) then then can't mess with the files outside of cvs. Outside of that, you're stuck with administrative policies ... esentially, asking them not to. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
