[Top][All Lists]

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

RE: Locking Branches patch

From: Chuck . Irvine
Subject: RE: Locking Branches patch
Date: Mon, 12 Feb 2001 10:13:49 -0600


The instructions are in the accompanying* files that should 
have been generated as a result of the make. Info files are 
documentation files that are read via emacs. You can do a search of 
"AlternateInfo" to find documentation relevant to this feature. 

The perl script gets called because it is configured to in the 
commitinfo file. The docs referred to above describe this mechanism.

Let me know if you have more questions.


> -----Original Message-----
> From: vic [mailto:address@hidden
> Sent: Sunday, February 11, 2001 8:37 PM
> To: info-cvs
> Cc: vic
> Subject: RE: Locking Branches patch
> On Sun, 11 Feb 2001 Irvine_Chuck_R/address@hidden wrote:
> > Vic,
> >
> > Attached are two files: John's patches for cvs-1.11 and his 
> commit info
> > perl script to implement branch locking. The patches 
> provide the hooks
> > that the perl script uses. You could, of course, write your 
> own script
> > if you prefer.
> >
> > It would be great if these patches could get merged into a future
> > release. If I had not found a way to implement branch locking, I am
> > pretty certain that eventually we would have been forced by 
> management
> > to use another SCM system that did provide this capability.
> >
> > If the CVS maintainers would care to comment on what it 
> would take to
> > get the patches merged in, I might be able to do the work required.
> Hi Chuck,
> Many thanks!  I now have a patched source and functioning binary, but
> how do I actually use the new features?
> Is the perl program supposed to act as a wrapper script for the actual
> cvs binary?  If so, can you give me an example of how it works?  Or is
> there at least some documentation that would tell me how to 
> actually use
> the branch locking, so that I could write my own script?
> Sorry for pestering with questions, but I'm new to CVS and 
> this feature
> just isn't documented.
> Cheers,
> Vic Gedris
> _______________________________________________
> Info-cvs mailing list
> address@hidden

reply via email to

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