Can I do a selective lock using this process, such that only certain branches are locked? What would my script look for if this could be done?
On Wed, Oct 10, 2001 at 12:59:46PM -0400, Brad L. Chisholm wrote: > You could also create a commitinfo trigger which returns non-zero, and > optionally displays a message indicating that check-ins are currently > disabled. Since read locks can occur in normal use, this also allows > the users to distinguish between a mandated lockdown, and just a normal > lock collision. > > -Brad > > On Tue, Oct 09, 2001 at 03:28:10PM -0400, Larry Jones wrote: > > [EMAIL PROTECTED] writes: > > > > > > � � � � � �I have set up a CVS as part of my project. At times I want to > > > lock the CVS for check-ins .But checkouts should not be locked. Is there a > > > way to do this in the CVS. Could any one help me to resolve the issue. > > > > You need to create a read lock in each directory in your repository. > > See the manual for technical details: > > > > <http://www.cvshome.org/docs/manual/cvs_2.html#SEC17> > > > > -Larry Jones > > > > Even though we're both talking english, we're not speaking the same language. > > -- Calvin > > > > _______________________________________________ > > Bug-cvs mailing list > > [EMAIL PROTECTED] > > http://mail.gnu.org/mailman/listinfo/bug-cvs > > _______________________________________________ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs -- [EMAIL PROTECTED] V-Net: 622-3286 Phone: 1-719-535-3286 Pager: 1-800-724-3624 # 140-1311 _______________________________________________ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
