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.
--
[ Picked text/plain from multipart/alternative ]
Hi guys.
I've been seeing the problems you have with the .perms and .owner file.
I do have the same kind of troubles.
What happen is that, when someone import a module, .perms and .owner file are automaticaly created in the subdirectories of the main directories.
For instance , if your program looks like :
myprogram/sub_dir1
/sub_dir2
when you import the program
cvs import -m "" myprogram vendor release
the .perms and .owner files will be created in sub_dir1 and sub_dir2 but not in myprogram.
Moreover, the .owner will contain the name of the user who imported the module and the .perms will have the default permissions set to rwc.
It would be really cool if these files (.perms/.owner) were also created in the main directory because, nowadays, when the user who imported the module want to change the user acces list, he must contact the administrator to change the rights for the main directory but he can change the rights for all subdirectories.
It would be great if he could do it for all the directories composing the modules he imported.
What do you think Tony ?
Hope this will help resolve this issue,
Sebastien Abras
Using
CvsNT 1.11.1.3 build 57c
WinCvs 1.3 beta8 upgraded with the cvs.exe and dll's from the server CvsNT 1.11.1.3 build 57c
--
_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs