How to fix issue when committing a change to CVS
You need to update your working copy first by running cvs up because someone has already updated these files while you were working on them. CVS can't automatically merge these changes during commit.
Additionally, just in case you may get error sometimes to UPDATE your local version. The final solution is :
1. Save your local code to another place manually
2. Revert the files which may have conflicts to the HEAD (most latest) version on CVS server.
3. Add back your change to the Reverted file.
The concept for above solution is to CLEAR UP all the possible issue by REVERT and get a 100% clean version from the repository then add back our changes.
It can resolve below issues which caused by code out of date / code base messed up.
- CVS commit had a conflict and has not been modified
- CVS update failed
- CVS not synced