Adrian Chapela: > > Now the copy on the repo is bad, because the User1 is using a function > which isn't on the file3 commited by the User2. Is there any way to > advice User1 that some other files are changed by another user ?
Apart from commit messages by mail: no.
Probably the best approach is to have a build system which regularly
checks out the latest changes and compiles the whole tree. This prevents
at least failures like the one you describe. If you add unit tests, you
can prevent even more errors from entering the production system.
J.
--
Watching television is more hip than actually speaking to anyone.
[Agree] [Disagree]
<http://www.slowlydownward.com/NODATA/data_enter2.html>
signature.asc
Description: Digital signature
