Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Thanks for your reply. Sorry for my poor English. Yes, I'm also a SA of company so I can operate the files on server. Hello.txt I mentioned is just hello.txt.v and sorry for my mistaken. I do all the operations of setting permission on cvs server. But I want to know how I can lock the files to let only the certain person can modify them. Thanks in advance. -----Original Message----- From: Bo Berglund [mailto:Bo.Berglund at system3r.se] Sent: 2003Äê8ÔÂ15ÈÕ 18:03 To: hodgen he; cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: RE: [cvsnt] Baseline and lock files Do you really understand how CVS works???? You should read up on the basics before going further. There are links on the CVSNT homepage to good info sources. You describe something that does not make any sense unless you have confused the repository and the checked out copy of a module. There simply are no files in the repository named as you decribe (hello.text). All files in the repository are RCS files with an extension of ,v, so your file would be hello.txt,v inside the repository. Using NTFS security inside the *repository* is simple and effective, but of course you have to be on the server doing this! Also NTFS can only handle the permissions on individual files and folders, not on certain revisions on a file. Revision handling is done through CVS and this again requires a thorough read of the available literature. Start with the Cederquist as a reference and Karl Fogels book as a user's perspective. And what do you mean by CI??? /Bo -----Original Message----- From: hodgen he [mailto:hodgen.he at bleum.com] Sent: den 15 augusti 2002 11:50 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] Baseline and lock files All, After I baselined the CIs, I want to lock some CIs to let only some person can modify them. Before I use pserver, I think that can't afford enough permission control. So I change to SSPI and log onto cvs server with my domain password. I want to set the file permission on cvs server with NTFS to control but failed. For example: CMTest repository has a folder named test. Under test there is a file named hello.txt. I found the default permission is everyone has full control. If I add my account and set him only read permission on hello.txt, I still can modify and commit the change. If I remove the everyone account on hello.txt, the same. But if I remove the everyone account on test directory, I can't commit the change. Then if I add my account with modify permission on hello.txt, I also can't commit the change. It seems that all the directory is locked and the permission is controlled by everyone account. How to do? Thanks. _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs