info-cvs
[Top][All Lists]
Advanced

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

RE: Question


From: Arthur Barrett
Subject: RE: Question
Date: Mon, 27 Sep 2004 23:08:06 +1000

The atomicity problem is solved if you use CVSNT.  CVSNT on Unix, Linux, 
Windows etc is open source and completely free.  It incorporates a lock server 
which guarentees that a single checkout or update operates on the repository at 
the point in time that it began.

You can download CVSNT for Linux, MacOS X, Unix and Windows from 
http://www.cvsnt.com/

Regards,


Arthur Barrett

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Gleidson Sá Barreto
Sent: Sunday, 26 September 2004 11:51 PM
To: address@hidden
Subject: Question


Now, I was reading a material about CVS technology and
I came across some doubts in concerns the some
concepts:

1-To take place the transfer of the files stored in
the repository q they were modified for your work
area, through a sicronização operation. Like this,
would to be in fact that sicronização operation? 

2-CVS counts with a mechanism capable to control the simultaneous accesses and 
the parallel modifications, guaranteeing like this the integrity of the 
modifications and atomicity of the operations. Would 
be in fact that atomicity of operations? 

3-CVS possesses mechanism capable to identify and to
solve conflicts. However those identified conflicts
are merely textual, not existing any analysis of the
logical consistence. Here I didn't understand the
expression textual conflicts very well. 

obs:those concepts were retired of the book CVS of
Cristiano Caetano.


        
        
                
_______________________________________________________
Yahoo! Messenger 6.0 - jogos, emoticons sonoros e muita diversão. Instale 
agora! http://br.download.yahoo.com/messenger/


_______________________________________________
Info-cvs mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/info-cvs




reply via email to

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