Aaron Kelley writes: > > Second, is there a way to compare all of local files with all of the > files in the CVS repository and get a list of files out of sink, files > that exist locally and not in the repository, and files in the > repository and not locally?
cvs -nq update > Third, what happens when a file is moved in the repository and someone > with a local copy does an update? Does their local file get deleted? > If not, do they have to delete it manually? The local copy gets deleted unless it's been modified -- if it's been modified, it's up to the user to decide what to do. > Fourth, can you control who controls can write to what files? What type > of permission control can be added? You can use normal filesystem permissions to control access on a per- directory basis. People need read and execute permission on the directory (and read permission on the files) to read stuff, they also need write permission on the directory (but not the files) to commit changes, add tags, etc. If you do want to allow read-only users, you'll need to use LockDir= in CVSROOT/config to put the lock files somewhere other than in the repository since read-only users still need to be able to create lock files. -Larry Jones Mom would be a lot more fun if she was a little more gullible. -- Calvin _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
