cvs

Delete file versions from the CVS repository

Steps:

1. After login to the server where the CVS repository is stored, go to the folder of the project:

cd [project_folder_path]

2. Delete the wrong revisions from CVS, for a specific file:

cvs admin -o [file_revision_number]: [file_folder_path/file_name]

The command "-o [file_revision_number]:" deletes all the file's revisions, starting from the specified number, including the respective revision and all the way to the end of the branch containing the respective revision.

Example:

cd /home/projects/myWebsite
cvs admin -o 1.10: public_html/calendar/availabilityView.jsp

Useful resources:
http://cvsman.com/cvs-1.12.12/cvs_133.php

Taggings:

Checkout specific file version from CVS

Steps:

1. After login to the production system server, go to the folder of the project

cd [project_folder_path]

2. Checkout the correct revision from CVS, for a specific file

cvs checkout -r [file_revision_number] [file_folder_path/file_name]

Note: The option "-r [file_revision_number]:" performs the checkout of the specified revision.

Example:

cd /home/projects/myWebsite
cvs checkout -r 1.14 public_html/events/localEventMenu.jsp

Useful resources:
http://cvsman.com/cvs-1.12.12/cvs_138.php#SEC138

Taggings:

Wrong CVS version of file updated in production system

Sometimes during development it can happen that files are wrongly updated in the production system. In order to avoid application errors and other malfunctions of the production system, the correct version of the file needs to be restored as soon as possible.

Wrongly committed file versions to CVS repository

When a new colleague is working for the first time with CVS, it can happen that he/she does mistakes when committing files to the repository. In case a file is wrongly committed (either once or multiple times) to the repository, then it is a good practice to clean-up the mistake and delete the wrongly committed file versions.
Subscribe to cvs