[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Multiple locks on a file
From: |
Christopher.Fouts |
Subject: |
RE: Multiple locks on a file |
Date: |
Fri, 15 Oct 2004 16:30:29 -0400 |
I'll look. Thanks!!!
>-----Original Message-----
>From: address@hidden
>[mailto:address@hidden On Behalf Of Todd Denniston
>Sent: Friday, October 15, 2004 4:26 PM
>To: Fouts Christopher (IFNA MP DC)
>Cc: address@hidden
>Subject: Re: Multiple locks on a file
>
>
>address@hidden wrote:
>>
>> 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
>>
>To me it is beginning to sound like you want the cvs_acls
>family of scripts from
>the contrib directory.
>look in
>INSTALLPATH="`dirname \`which cvs\``"; \
>ls $INSTALLPATH/../share/cvs/contrib; \
>echo $INSTALLPATH/../share/cvs/contrib
>
>if you don't find that get a copy of the source and look in to
>the cvs-[version]/contrib/ directory.
>
>for a while I think there was a cvs_acls2 script running
>around in the mailing list that might have been better if you
>don't find it in the source.
>
>> >-----Original Message-----
>> >From: Larry Jones [mailto:address@hidden
>> >Sent: Friday, October 15, 2004 3:34 PM
>> >To: Fouts Christopher (IFNA MP DC)
>> >Cc: address@hidden
>> >Subject: Re: Multiple locks on a file
>> >
>> >
>> >address@hidden 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
>> address@hidden http://lists.gnu.org/mailman/listinfo/info-cvs
>
>--
>Todd Denniston
>Crane Division, Naval Surface Warfare Center (NSWC Crane)
>Harnessing the Power of Technology for the Warfighter
>