-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Paul Sander <[EMAIL PROTECTED]> writes:
> On Sep 8, 2005, at 3:10 AM, Mark D. Baushke wrote:
> > Andy Jones <[EMAIL PROTECTED]> 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.
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFDIHXBCg7APGsDnFERAvoUAKC+FAFg7Rzqv94VaeWtPiohf0wEkwCgiRVY
kH/czCAbt8mfOl1HyxtkkWg=
=4ONj
-----END PGP SIGNATURE-----
_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/info-cvs
