[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: how to 'lock down' a branch?

From: Shubhabrata Sengupta
Subject: Re: how to 'lock down' a branch?
Date: Tue, 5 Jun 2001 13:47:42 +0530


               I am aware of that patch you are referring to - I found it
when I was searching for a way to lock branches. The problem with the setup
that I have here is - I am not allowed to patch the CVS server - that is
controlled by a separate group - and they would be extremely unhappy if I
wanted them to put in a patched CVS server. However I found out that the
'branch locking' behaviour is not very hard to implement even without the
patch - the commitinfo scripts always have access to the CVS/Entries file
and it is quite easy to use some awk/sed magic to extract the branch
information for the file that is going to be checked in - the name of the
file that is going to be checked in is always passed to the commitinfo
script. I has posted a sample script which locks branch in the aformentioned
way on the mailing list sometime back.



-----Original Message-----
From: address@hidden <address@hidden>
To: address@hidden <address@hidden>;
address@hidden <address@hidden>; address@hidden
Date: Monday, June 04, 2001 11:32 PM
Subject: RE: how to 'lock down' a branch?

>Sometime ago, I posted patches by John Cavanaugh that can be used for
>branch locking. The patches are for version 1.11 of CVS but work for the
>most current version as well. One chunk of the patch will fail because a
>file has been removed (actually, merged into another), but I have
>verified that this causes no problems. If you'd like to have a look at
>the patches, search for my name in the mail archive and you should be
>able to find them. The patches include updates to the texinfo file which
>describe the new functionality. After you've patched and built, do a
>search of the cvs info files for AlternateInfo to get info on the new
>functionality. Basically, the patch causes more info, including branch
>name, to be passed to your commit info script. Included with the
>patches, is a perl script that can be specified in your commitinfo file
>to implement branch locking.
>-----Original Message-----
>From:    Shubhabrata.Sengupta
>         [mailto:address@hidden
>Sent:    Tuesday, May 29, 2001 10:18 PM
>To:      Harald.Kucharek; info-cvs
>Subject: Re: how to 'lock down' a branch?
>Ah! well - to prevent users from mistakenly doing checkins to a branch,
>along which you do not want any development to happen. This happens
>especially in large, geographically distributed teams when people tend
>forget that checkins are not permitted along certain branches for
>reasons - like product released from that branch is End-of-Lifed or that
>branch was created to do some experimental coding on a particular module
>etc. There possibly are various ways of spreading this information among
>team members and have other methods of enforcing them - but "locking
>branches happens to be a very convenient one.
>-----Original Message-----
>From: Harald Kucharek <address@hidden>
>To: address@hidden <address@hidden>
>Date: Tuesday, May 29, 2001 7:58 PM
>Subject: Re: how to 'lock down' a branch?
>>Kevin Yang wrote:
>>> Hi,
>>> Can I 'lock down' a branch in cvs? I need to do it so no check-ins
>>> happen to a release branch. It basically becomes a 'read-only'
>>> Thanks,
>>> Kevin
>>Why do you want to have this? Usually, when you make a release, you tag
>>the current state of the branch so you can revert to the release state
>whenever you want.
>>But you keep it accessible in case you have to do and check-in some
>> iXpoint Informationssysteme GmbH #
>>           Daimlerstr. 3          # Harald Kucharek
>>          76275 Ettlingen         # address@hidden
>>    Tel/Fax +49 7243 3775-0/77    #
>>Info-cvs mailing list
>Info-cvs mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]