[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS versus RCS
Noel L Yap
Re: CVS versus RCS
Wed, 22 Nov 2000 15:40:57 -0500
You can take a look at "cvs admin -l" (not advised since the admin stuff will
likely "go away" in the future) or use the "cvs edit -c" family of patches
available at SourceForge under project RCVS.
"cvs edit -c" isn't real locking in that it depends on the user using the "-c"
option and a "cvs edit -f" will override any "edit -c" lines in .cvsrc.
However, it does increase the likelihood that your developers will communicate
among each other thereby still allowing concurrent development without foregoing
the benefits of serial development -- you get the best of both worlds.
address@hidden on 2000.11.21 07:10:59
cc: (bcc: Noel L Yap)
Subject: CVS versus RCS
I'd like to use CVS.
The RCS handbook says :
RCS and CVS have totally different philosophies with regard to how to prevent
conflicting updates. While RCS enforces a strict rule that no two users
simultaneously update a source file, CVS takes a more pragmatic view that it is
sometimes necessary to allow to users to simultaneously work on the same file."
I don't want simultaneous access. How can I change the CVS settings (or
configure options ?) to make CVS acts like RCS, at least about this "problem".
Info-cvs mailing list
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 & Co. Incorporated, its
subsidiaries and affiliates.
- CVS versus RCS, Arnaud De Timmerman, 2000/11/21
- Re: CVS versus RCS,
Noel L Yap <=