The flags to update are optional

Cvs not updating latest revision

None of your changes

If you want to maintain several releases in parallel, you need to use a branch see section Branching and merging. Useful for seeing who made a particular set of changes. Working revision lists the revision of the working file which is the repository revision at the time you last updated the file. To incorporate your changes into the repository, use cvs commit. To avoid confusion, the word version is almost never used in this document.

You can reset them using cvs update -A. The repository, which is visible to everyone Local copies, which are visible to you Before doing anything else, you'll need to checkout a local copy of the repository files.

There are a variety of other useful cvs commands. Up-to-date The file is identical with the latest revision in the repository for the branch in use. Merging Revisions Normally, it's best to edit files in the directory that you're using for checkouts. The dilemna - you'd like to incorporate what you've done, but your copy of the file is now out of date.

If you can't determine the revision, this approach won't work, and you'll need to do a manual merge. Find out what revision your copy of the file is based on. Changes can be made to files here, then put back committed to the repository.

The commands must be issued inside

Of course, you might encounter merge conflicts that you will need to resolve before committing. However, the file will no longer appear when you do checkouts or updates. Files and directories are added with the cvs add command. And if you don't have local modifications then you can update cleanly.

The commands must be issued inside your working directory. None of your changes will be visible to other users until after you've committed them. We won't worry about that now.