[Top][All Lists]

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

RE: CVS - blocking commits

From: Bulgrien, Kevin
Subject: RE: CVS - blocking commits
Date: Tue, 30 Aug 2011 13:33:17 -0500

> -----Original Message-----
> We are done with our dev on the trunk and the version I have
> now is the one we will probably want.  I'd like to stop users
> from committing to the trunk.   Can I do this in some
> configuration file?
> in case in matters - it is cvs implemented on linux:
> Concurrent Versions System (CVS) 1.11.22 (client/server)
> KM

It seems unusual to want to block commits to trunk.  One normally
uses the cvs tag command to mark the point were development has
reached a stable point, then when you want to distribute the files
in that state, that are accessed using the tag.

The tag provides the control.  It matters not whether anyone
commits beyond the tag point.  They can continue to do bug fixing,
enhancement, etc. without impacting the state of the files at the
tag point.  Those changes will not be associated with the tag.  A
process should make it clear that official copies of files are
always marked with tags.  cvs export can be used to copy the tagged
files to distribution media, or perhaps the end-use location could
do a forced update (cvs update -C, for example) to the tag if it
was using a cvs checkout.

If you do want to truly block commits, you could craft a pre-commit
hook to prevent all commits, but again, I'd encourage a study up on
the appropriate use of tags before looking at doing that.

See for
information on the hook files (Trigger Scripts).

Kevin R. Bulgrien

This message and/or attachments may include information subject to GD Corporate 
Policy 07-105 and is intended to be accessed only by authorized personnel of 
General Dynamics and approved service providers.  Use, storage and transmission 
are governed by General Dynamics and its policies. Contractual restrictions 
apply to third parties.  Recipients should refer to the policies or contract to 
determine proper handling.  Unauthorized review, use, disclosure or 
distribution is prohibited.  If you are not an intended recipient, please 
contact the sender and destroy all copies of the original message.

reply via email to

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