info-cvs
[Top][All Lists]
Advanced

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

Re: Commit inconsistency: Up-to-date check did not fail though it sho ul


From: Kaz Kylheku
Subject: Re: Commit inconsistency: Up-to-date check did not fail though it sho uld have !
Date: Wed, 19 Feb 2003 01:54:35 -0800 (PST)

On Wed, 19 Feb 2003, Fabian Cenedese wrote:

> Well, I also commit single files for the same reasons (even if that makes
> me an idiot too). But before committing I sure do a test/update if there
> has anything changed in the repo. So I do the same as cvs ci on whole
> sandbox, just manually. 

I believe that it is not the same thing. The cvs ci operation is an
atomic test and set: it acquires a lock over what you are trying to
commit, checks that it's up to date, and then if so, it completes the
commit before releasing the lock.

Doing a separate update operation just before a selective commit
creates a race condition because the lock is not maintained across
both operations; you are thus relying on winning a race, however great
the odds may be in your favor due to the small time window.





reply via email to

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