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 email@example.com.
Dries Feys wrote: > Yes, indeed it goes much much faster to read the read-only flag, BUT when > an edited file is changed by another user, and some fancy scheduled task > merges those modifications in your file which is beeing edited, the > read-only flag get read-only again. You have to re-edit that file again. > With other words : some files may not apear in the list. (unless I can > set cvsnt that the file remains r/w after a succesfull merge) I think the only way a file would become read-only is if this merging task does a commit -- which I think would be a bad thing. Are you sure that it's just merging that makes an edited file read-only? > Another issue is that they want to see whether the "editable" files are > new files, not known to cvs yet or cvs-files in edit, but that I can check > with the files in the CVS subdirectory. Just a thought... Did you have a look at WinCvs? It has some of this built in. Gerhard