[EMAIL PROTECTED] on 2000.08.07 12:48:08
>I've been watching the exchanges here about this, and while I don't want
>to start any wars, I'd like to get a clarification about something.
Apparently not long enough. Read on.
>As I understand the CVS manual, the only way to have exclusive locks on
>checkout is to combine cvs checkout with cvs admin (there's a race
>condition there, right?). From what I've been reading (not necessarily
>just the manual), my impression is that this facility (exclusive
>checkout) may go away in the future. I'd like to know if that's correct.
Take a look at the "cvs edit -c", "cvs edit -f", and "cvs ci -c" patches in
SourceForge under the RCVS project. They aren't completely exclusive (ie the
"locks" are exclusive as far as everyone uses "cvs edit -c" and they can be
overridden with "cvs edit -f"), but they are good enough for most (if not all)
development. The only time (AFAICS) they aren't good enough is when there are
rogue developers who don't pay attention to set policies.
>I really don't want to debate whether that's a good or bad decision, I'd
>really just like to know if a) my understanding about this is right, and
>2) it's supportable in the long term without capturing and maintaining
>some version of CVS internally.
Unless standard CVS adopts the patches (and I really hope they do since, IMO,
they don't hurt the architecture or design goals of CVS at all -- although they
may break the offline mode of "cvs edit" since I had no way of testing it),
you'll have to maintain a site-specific copy of CVS yourself.
>I'd appreciate your indulgence on this. I've been reading documentation
>and playing with it for a few days now, but I'm not sure if I'm even
>asking the question correctly.
The right question is, "What are reserved checkouts for?" The cheap,
non-informative, and not completely correct answer is, "To stop concurrent
development." The real answer is, "To control development such that those
working on the same file are encouraged to work together." The patch is meant
to change CVS such that users are encouraged to communicate when working on the
same files. So, so long as there is good communication within the group,
concurrent development can still resume without the downsides of developers not
knowing what else is going on.
Noel
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.
