Updateing changes performed by other developers

In case you noticed that other developers changed the repository - fortunately you will be noticed by a mail to the developer mailing list if that is the case - you should get those changes to your sandbox. This is accomplished using the update command of CVS.

Example A.4. Updating the sandbox

To update the local sandbox the following command is used. As most other CVS commands, it operates recursively from the current working directory in the sandbox.


  thb:~> cvs -q upd
  U README
  M knewbankdlg.cpp
  thb:~>

The above shown output has the following meaning: the file README is udpated (U) from the repository to the sandbox because it has been changed by someone else in the meantime. The contents of the file in the sandbox will be replaced by the contents of the file in the repository, because it has not been altered in the sandbox. The file knewbankdlg.cpp has been modified (M) in the sandbox and needs to be returned to the repository.

If you run the same command again, the output will change, as the file README is now up-to-date.


  thb:~> cvs -q upd
  M knewbankdlg.cpp
  thb:~>

Sometimes it is useful to get an overview of what the status of certain files in the repository is without modifying the sandbox (updating). This can be accomplished by using the -n option to the update command.

Example A.5. Checking the status of files in the sandbox


  thb:~> cvs -nq upd
  U README
  M knewbankdlg.cpp
  thb:~>

The status of the files is the same as explained above, but the file README will not be updated. It remains unchanged in the sandbox. If you run this command again, the output remains.

Prev:	Home	Next:
Checking in to the repository	Up	Dismissing changes