Could commit operation cover others' modification without conflict warning?

Question

I seldom execute update operation before commit because I think once others have modified the file already, then when I commit that file the conflict warnings would occur. At least I wouldn't cover others' submission.

But is it possible that I might cover others' submission without warning message when using commit operation?

In other words, must I always execute update operation before commit to avoid covering others' submission?

Answer 1

You should always update, for sure. Otherwise, under normal conditions (every project is different), how can you make sure that your changes are working fine with other developer's changes? It's not a matter of only conflicts. Say, a java project. You add a class import to the class that you are working on.... but then on one of the recent revisions from other developers, that class you are importing is gone.... you will commit, no conflict whatsoever but the project is busted .