[Top][All Lists]

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

Re: [Non-DoD Source] Re: CVS lock issue

From: Spiro Trikaliotis
Subject: Re: [Non-DoD Source] Re: CVS lock issue
Date: Thu, 15 Feb 2018 21:27:02 +0100
User-agent: NeoMutt/20170113 (1.7.2)

Hello Steven,

* On Thu, Feb 15, 2018 at 08:20:38PM +0000 Glasgow, Steven R CIV USARMY TRAC 
(US) wrote:
> Could it be possible that two developers tried to tag the file at the
> same time?  I thought CVS handled that situation.

It is enough that two developers try to do anything on the same file,
and you will get that message.

As CVS cannot guarantee "atomic" operations, that's the way it handles
such problems: It gives you an error, and you have to look what it did,
and what it did not, and how you can resolve this.

This is one of the reasons CVS is essentially abandoned nowadays, and
replaced by SVN (which can handle atomic operations), or even other
tools like git, mercurial, and so on.

> Could it be possible that one developer created the lock and a second
> one was not able to do that (file exists).  I thought the first
> developer would have created  the #cvs.lock directory making the
> second developer wait to even access the <path> directory.

No, unfortunately, that's not how CVS works. There is no wait for the

Best regards,

Spiro R. Trikaliotis

reply via email to

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