> I normaly don't want to use locking on the cvs archive. > On Windows projects I think it's simplier to use strickt locking on > the resource and the corrosponding header file. Merging changes in > that files does not make happy anyone :-) > If not how can I enshure that these files can only be checked out > locked? > Files should be read only upon someone uses cvs edit. Noone should be able > to use a cvs edit upon the first editor uses cvs unedit.
Use Noel Yaps edit -c patch (it is builtin for cvsnt; for the *x version you must apply it yourself) and do a 'cvs watch on' on the Resource.h files. See my post to this list of December 10 this year. If you're interested, I can post a script which does the watch on automatically for filenames matching a certain regex, when they are first added to the repository. Paul Gelderblom _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
