As the code integrator, I just lock the HEAD and the development branch to prevent users from submitting directly into them. I am enforcing a 3-tier branch system...
trunk <--> dev_branch <---> priv_branch. Users (only 4, so this works) submit daily work into private brances; we integrate at least once a week into the development branch, which is regression tested. After a certain period, I merge the dev. branch into the trunk. This has worked for me so far, and may NOT be for everyone. -chris >-----Original Message----- >From: Larry Jones [mailto:[EMAIL PROTECTED] >Sent: Friday, October 15, 2004 3:34 PM >To: Fouts Christopher (IFNA MP DC) >Cc: [EMAIL PROTECTED] >Subject: Re: Multiple locks on a file > > >[EMAIL PROTECTED] writes: >> >> First off, I "should" be able to have multle versions locked >correct? >> For example, I should be able to lock a branch and a trunk >version of >> the same file. > >Correct. > >> Secondly, how can I force cvs to unlock ALL versions? I did have a >> checkout branch version of proj. > >You can't -- you have to unlock them one at a time. It's the >*Concurrent* Versions System, you shouldn't be using locks. > >-Larry Jones > >Don't you hate it when your boogers freeze? -- Calvin > _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
