Robert, Well in CVSNT (free/GPL just like CVS) on Linux/Windows/Solaris/HPUX etc you just mark the repository read-only in the /etc/cvsnt/PServer configuration file.
But of course if you were using CVSNT you'd know it has ACL's, Audit, Mergepoints (Merge Tracking), True Rename (not copy+delete), Unicode filenames, Unicode Merge etc. ie: all those features that are yet to make it into SVN: http://subversion.tigris.org/roadmap.html Regards, Arthur Barrett -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Dodier Sent: 15 February 2006 04:36 To: [email protected] Subject: disable cvs commit and/or make repository read-only Hello, I am considering converting an existing CVS repository to Subversion. After that I'd like to make it impossible to commit stuff to CVS to avoid heartbreak, confusion, etc. What is the standard practice for making a CVS repository read-only? I've searched this ng for ideas and didn't come up with anything clear to me. One idea was to modify the file system permissions but wouldn't it be better to do it through CVS itself? (Instead of letting CVS try to commit stuff and fail.) Anyway I welcome your comments. Robert Dodier _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
