If 1. developers are in the habit of doing a "cvs edit" on files they're about to modify (with the intent of committing those modifications) 2. "cvs watch on" has been done for that module or file 3. CVSROOT/notify and CVSROOT/users has been setup correctly those already editing the file will be notified of actions (ie edits, unedits, commits) done on that file. With the patch, "cvs edit -c" will first check to see if anyone is already editing the file. If so, the edit aborts. The check can be overridden with "cvs edit -f" (supposedly after the new editor has contacted the existing editors to see if their modifications will logically conflict). Noel [EMAIL PROTECTED] on 03/24/2000 09:02:24 PM To: [EMAIL PROTECTED] cc: Subject: Re: binary files: checkout methodology: enforce only one tomodify ? I've heard this patch mentioned a few times. What does it do? Noel L Yap wrote: > > You can use the "cvs edit -c" patch and have all your developers use a procedure > that uses it. > > Noel
