[Top][All Lists]

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

Re: CVS Transaction

From: Paul Sander
Subject: Re: CVS Transaction
Date: Thu, 8 Sep 2005 14:12:56 -0700

On Sep 8, 2005, at 10:32 AM, Mark D. Baushke wrote:

Hash: SHA1

Paul Sander <address@hidden> writes:

On Sep 8, 2005, at 3:10 AM, Mark D. Baushke wrote:
Andy Jones <address@hidden> writes:
There is also the theoretical issue of
multiple developers committing changes to the
same set of multiple files at once, which
does rather worry me.

It should not worry you. cvs gets it correct.
Read the manual on how cvs does locking.

The existing locking system assumes that
everything underneath is working and everything
is allowed to run to normal completion. In the
event of temporary failures such as network
outages or power interruptions, or even if the
user types ctrl-C, you see partial commits
recorded in the repository after the customary
clean-up of the locks.

Yes, that is true. The user may abort during the
commit operation. However, a network outage should
between client and server will still see the
commit finish is most cases. Power failure on the
server will potentially leave you with stale locks
and partially committed files.

Network outages, if they're long enough, or if they involve certain failure points, will cause the connection between client and server to terminate. In such cases, partial commits can also be stored.

reply via email to

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