Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
thanks for your answer. I agree that if a "revision" is committed, it is no longer locked. (because locks are specific to revision) Now I'm not sur that if a "file" is commited, it is no longer locked. According to my test, if a file (any revision) is commited and has only one revision locked, it is no longer locked. If a file has 2 revisions locked and one of these revisions is commited, file is no longer locked (both revisions are unlocked). But if a unlocked revision is committed, file is still locked (both revision skeep locked). Moreover if a file has 3 revisions locked and one of these revision is commited, file is still locked (the 2 other revisions keep locked) Is this a bug or normal behaviour ? thanks Loïc ----- Original Message ----- From: "Tony Hoyle" <tmh at nodomain.org> Newsgroups: support.cvsnt To: <cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook> Sent: Tuesday, August 12, 2003 6:06 PM Subject: Re: [cvsnt] Is this a CVS bug ? > On Tue, 12 Aug 2003 17:32:38 +0200, Loïc Bertholet <lbertholet at sysdeo.com> > wrote: > > >Hi, > > > >I have some problem to understand how lock are lost when a resource is commited. > > > If a file is committed, it is no longer locked. > > Locks aren't really supported anyway. There are reserved checkouts for those > cases where it's essential (binaries, generally). > > Tony > > _______________________________________________ > cvsnt mailing list > cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs >