RE: [Phpgroupware-developers] Managing changes (was: PHPDocs for head)

[Guillaume Courtois]

> Well, perhaps it's a good habit - especially when working on an app for
> months - to a) have an eye on the cvs commit mailing list to see whether
> anything has been committed to that app in the meantime and b) do a "cvs up"
> from time to time and definitely before any "cvs  co" to actually take
> advantage of those changes and fixes.
>
> That's the whole purpose of CVS that more than one person can actually work
> simultaneously on the same code. If we skip that, we do not need CVS at all.
> Otherwise you can better use things like M$ VSS which uses exclusive
> checkouts; i.e.: as soon as one dev has checked out a file, noone can commit
> to it any more until the first one has released it again.

I always do that way. That seems impossible others don't !