I think the problem any VC system is supposed to solve is to prevent multiple
people from editing the same file at the same time. CVS does this. Instead,
people edit different copies of the same file at the same time. The first
person to checkin succeeds. CVS will prevent checkins by others and will
display a message saying that they'll have to perform a merge (via cvs update).
Noel
[EMAIL PROTECTED] on 2001.01.31 03:07:34
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: "Concurrent" VS...
Requiring Version Control, I have installed CVS for evaluation. (I
have used SCCS in the past but systems are different here now.)
One of my principal reasons for using a VC system is to avoid the
version discrepancies that arise from two separate developers
inadvertently editing the same file at the same time.
Have I selected the wrong VC system?
Cheers,
James.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co. Incorporated, its
subsidiaries and affiliates.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
