Re: how to 'lock down' a branch?

[Shubhabrata Sengupta]

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 to
forget that checkins are not permitted along certain branches for various
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 the
team members and have other methods of enforcing them - but "locking down"
branches happens to be a very convenient one.

Thanks

Shubho

-----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 can
>> happen to a release branch. It basically becomes a 'read-only' branch.
>>
>> 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
bugfixes.
>
>Harald
>
>--
> iXpoint Informationssysteme GmbH #
>           Daimlerstr. 3          # Harald Kucharek
>          76275 Ettlingen         # address@hidden
>    Tel/Fax +49 7243 3775-0/77    # www.ixpoint.de
>
>_______________________________________________
>Info-cvs mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/info-cvs
>