Re: How can I administratively "freeze" a branch?

[Todd Denniston]

address@hidden wrote:
> 
> >   Why not just "cvs rm" all the files from it, so they no
> > longer exist at the head of the branch?  People would have to
> > accidentally checkout old revisions before they could
> > accidentally commit to it; that's pretty improbable I think.
> 
>   The problem is that files from old branch still exist in
> HEAD (in fact, what we did was to commit the branched files
> to HEAD).
> 

I believe cvs_acl used as a commitinfo script, would give you the ability to
lock a branch.
on a fedora core system `locate cvs_acl` shows a copy to be in
/usr/share/cvs/contrib/cvs_acls
or you could get a ".in" copy from:
https://ccvs.cvshome.org/source/browse/ccvs/contrib/cvs_acls.in?rev=1.7&only_with_tag=HEAD&content-type=text/vnd.viewcvs-markup


Because the originating message was sent to a mailing list which is sent to
many people and archives for posterity, plus it appears to be expected the
original sender desired an answer, the following disclaimer is being
ignored, i.e., please direct your PHB and legal team to:
http://www.goldmark.org/jeff/stupid-disclaimers/
before people start ignoring your pleas for help. (some people explicitly
disclaim the disclaimer that its attached to their emails.)
If they realy must have one try:
http://www.goldmark.org/jeff/stupid-disclaimers/#sec-least-stupid

> This message is for the designated recipient only and 
> may contain privileged, proprietary, or otherwise 
> private information.  If you have received it in error, 
> please notify the sender immediately and delete the 
> original.  Any other use of the email by you is prohibited.
> 

-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter