DZ-Jay wrote: > On Oct 5, 2007, at 02:49, Olivier Sannier wrote: > > SubVersion on the other hand was created to enable more efficient > collaboration, purely as a source control tool. You can mark files > with "requires lock", which will require a developer to acquire a lock > before committing changes. We use this mostly for sensitive files > where a merge gone awry may be critical; or for project documentation, > which should not change that often. In the case of ICS, for example, > *if* you were to use locking, I would suggest it on the highest files > of the TWSocket class hierarchy, which if changed, may affect all > other units. That way you make sure that, say, Francois and Arno > will not be changing the same things at the same time.
Isn't it safe to use the Copy-Modify-Merge solution, described in the online-help ? -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be