Rich Salz wrote:
>
> Is it possible to lock a branch, or somehow make it "read-only"
> so that no further check-ins can be done on it? In perusing
> of Cvedarquist and cvsbook.red-bean.com I can't find it.
>
> Locking branches (actually "obsolete -lock") is a common
> ClearCase practice that would be nice to have here.
>
> If not, this seems to fit into the CVS philosophy:
> 1. Define a new special tag (cf HEAD) called LOCKED.
> 2. This tag is always sticky.
> 3. On checkout, if the version is tagged LOCKED, then
> (try to) remove write permission.
> 4. On checkin, fail if the version was tagged LOCKED.
>
> Comments?
> /r$
Indeed, locking down branches is a VERY useful feature. This article
describes how one person has already implemented it - let us know what you
think:
http://www.egroups.com/message/info-cvs/16893?
--
Peter Wolfe Tel: (604) 303-2300
Telos Engineering Limited, http://www.telostech.com
120 - 13120 Vanier Place, FAX: (604) 276-0501
Richmond, BC, V6V 2J2. email: [EMAIL PROTECTED]
