On Tuesday, February 15, [EMAIL PROTECTED] wrote:
>
> Let me ask: what is it about locking and concurrency that makes
> them mutually exclusive? Other software manages to find design
> patterns that allow them to handle configurable policies. (The
> X11 mantra "mechanism not policy" is a great example) Why not CVS?
> Why not let the repository maintainer choose their policy?
Sure, why not. Draw up a proposal for CVS V3.0, make sure it addresses
all the issues that have been hashed to death on this list. Make sure
it keeps everybody happy, and the clincher, make sure it is at least
marginally backwards compatible client-server wise to the current source
of 1.10 (1.9 preferable...)
Once that is done, then if you can invest (or the general public) some
$50'000 for the first 3 years, plus 5 full-time programmers, you shall
have your X11-type system. It's a noble goal, but my 5 hours of "free"
time a week are not going to cut it...
> Configurable
> Versioning
> System
>
> (think anyone would notice?)
Yes. Take a look at the linecount, and compare it to the X11 system...
--Toby.
