Re: Branch Locking

[Greg A. Woods]

[ On Friday, August 24, 2001 at 09:40:14 (-0700), Kent Henneuse wrote: ]
> Subject: Re: Branch Locking
>
> A potential fix or way to workaround branch locking not being in CVS
> is to create a script in commitinfo to check whether the file is going
> in on a specific branch.  I have not implemented this nor have I even
> toyed with commitinfo to see what sort of information is passed, but
> from all I have read it seems like a method for doing this.

I too would go with commitinfo to implement branch locking.  It can be done.

> I am not sure about discontinued branches though.  In a previous life I 
> saw branch locking used to control who was allowed to checkin fixes to 
> a release.  This way only approved fixes were allowed in for making a 
> patch from the branch.  I know that Perforce has this sort of mechanism
> but it is probably is because you finer control over users.  Not having
> dug to deep into CVS in this area I can't say for sure.

I would implement discontinued branches in the same way:  with commitinfo

However there's also the possibility of using a really simple hack that
applies rules based on a tag naming convention too.  Simply disallow
commits if the branch tag either starts with, ends with, or contains,
the word "discontinued" or some abbreviation thereof.  Then you just
rename a branch to match the disallowed pattern when you want to
"discontinue" it!  ;-)

[[ I don't seriously think such a hack should initially be in the main
public CVS sources, but it's a simple enough patch that someone could
easily create and maintain independently.  ]]

-- 
                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>