info-cvs
[Top][All Lists]
Advanced

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

RE: How to lock CVS for check-in


From: Pyatt, Scott
Subject: RE: How to lock CVS for check-in
Date: Wed, 10 Oct 2001 14:56:53 -0700

"How to lock a branch?"  This seems to be the number one question posted to
info-cvs.  I posted it myself two years ago.  Is there anyway this
enhancement can get rolled into a future release of cvs (e.g., 1.12)?  If
not, is the fear that it may break existing commitinfo scripts?

Thanks,
-Scott

-----Original Message-----
From: Brad L. Chisholm [mailto:address@hidden
Sent: Wednesday, October 10, 2001 1:15 PM
To: David Everly
Cc: Brad L. Chisholm; Larry Jones; address@hidden; address@hidden
Subject: Re: How to lock CVS for check-in


You can selectively lock branches, but only if the branch info can get
passed to your commitinfo script.  We have "enhanced" the commitinfo
interface locally to send additional parameters we find useful, including
the branch info.  I'd be happy to send the diffs (commit.c), if anyone 
is interested.

-Brad

On Wed, Oct 10, 2001 at 11:57:25AM -0600, David Everly wrote:
> 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:
> > > address@hidden 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
> > > address@hidden
> > > http://mail.gnu.org/mailman/listinfo/bug-cvs
> > 
> > _______________________________________________
> > Info-cvs mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/info-cvs
> 
> -- 
> address@hidden
> V-Net:       622-3286
> Phone: 1-719-535-3286
> Pager: 1-800-724-3624 # 140-1311

_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs



reply via email to

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