[EMAIL PROTECTED] on 02/16/2000 04:38:03 AM
>>> But that is the problem, each and every developer doesn't know who all the
>>> other developers are.
>>
>>I'd like a little clarification on what the environment is that you're
>>developing in, that this is the case?
>
>There are two situations that makes this "mess".
>1. The developers are situated at different sites, working at different
>times etc.
"cvs edit" works just fine for this.
>2. Some of the code are libraries that no one thought anyone else was
>working with, but they needed a quick improvement.
I'd probably use the "cvs edit -c" patch for this.
In fact, considering that it's rare that developers edit the same files at the
same time and the "cvs edit -f" command (that accompanies the "cvs edit -c"
patch), there's no reason not to put "edit -c" in your .cvsrc file.
The downside, I think (since I haven't tested this situation), is that "cvs
edit" will stop working if the server can't be contacted. But I haven't heard
anyone either complain or confirm this.
Noel
