|
From: | Todd Denniston |
Subject: | Re: disable cvs commit and/or make repository read-only |
Date: | Tue, 14 Feb 2006 18:44:58 -0500 |
User-agent: | Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) |
Robert Dodier wrote:
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.
file system permissions are the usual manner, set the directory permissions to read-only (note you'll need to do it inside to out :), this should be enough and it is well understood by the CVS crowd.
other things you can do is put the following line in the taginfo and commitinfo config files to prevent cvs from allowing commits and tags:
ALL /bin/false -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter
[Prev in Thread] | Current Thread | [Next in Thread] |