>>
>> Yeah, that's another issue, he rejects the whole notion of concurrent
>> versioning, i.e. checkout-modify-merge. He has insisted that he will
>> never do anything except lock-modify-commit-unlock.
>>
Is he one of those guys that locks that whole world so that everyone else
has to do all the merging, is he ;)
I really don't see any benefits in lock-modify-commit-unlock. If different
developers are not working on the same files then it buys you nothing. If
developers *are* working on the same files then the processes is actually
merge-lock-modify-commit-unlock. Also, with lock-modify-commit-unlock I find
that many developers will lock more files than they really need just to make
sure that they don't have to merge (in other words making sure that others
do have to merge.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 29 19:07:49 2007