Hi mitch,
thank you guys for responding. The whole idea is yes, the merge-based model
of CVS is great as far as you can trust people that develop with you. Once
you integrate other people in the team, a great deal of communication must
be sent to responsabilize them. In that case you may need exclusive locks.
cheers,
Stan.
At 01:59 AM 4/19/00 -0500, Mitch Davis wrote:
> > Reserved locks are usually (if not always) used to coordinate
> > developers.
>
>For what it's worth, people who ask me about CVS' ability to lock
>files are invariably those who are comfortable with the RCS locking
>model, and have not had sufficient practical CVS exposure to realise
>and trust just how well CVS' merge-based model works in practice.
>
>The whole idea of locking files encourages "silos of responsibility",
>where each person only knows their part of the system. The nice
>thing about CVS is that no-one knows you've modified a file until
>you're good and ready to announce it.
>
>Regards,
>
>Mitch.
>--
>| mailto:[EMAIL PROTECTED] | Not the official view of: |
>| mailto:[EMAIL PROTECTED] | Australian Calculator Opn |
>| Certified Linux Evangelist! | Hewlett Packard Australia |
