CVS — a 1 or 2-day course
The outline for this course is currently undergoing review. Details will be published online as soon as possible. The new format for the CVS training will be similar to that of the Subversion training.
Synopsis
We offer six CVS course modules, which can be combined to form a one or two-day course
depending on requirements. Approximately two hours per modules should be allowed, so
three of four modules can be taught per day.
The CVS for Users modules start from the very beginning and take new users of CVS
through the most important techniques for managing files and revisions.
It starts with using the cvs command-line program, but can
also cover the GUI interfaces WinCVS or TortoiseCVS if required.
The CVS for Administrators modules cover the features of CVS which aren't needed
for normal work (with a pre-configured CVS system) but are required to admin a CVS
server, resolve user problems with using CVS, and get the most out of
CVS with it's more advanced features. Please note 'CVS Server for Administrators' and
'CVSNT Server for Administrators' are very similar modules.
The CVS and Subversion Compared module is suitable for non-CVS and non-Subversion users
who want to see the differences between the two in depth, or else for users and
administrators with one system who want to convert to the other.
Suitable for
Teams of software developers and programmers who need to work co-operatively
on projects.
System administrators who need to install and maintain the CVS
software and CVS repositories.
Prerequisites
- An understanding of the code-management issues in team-based software
development
Delivery
Instructor lead in-house training with a great deal of hands-on
practice.
Publicly scheduled dates, locations, and prices
A schedule of dates for this course is not currently available. Please call 0800 651 0338 or use our contact form to enquire about places and availability.
Course Contents
CVS for Users 1
- An Overview of CVS
- Basic concepts
- Accessing a repository
- Checking out a working copy
- Making a change
- Finding out what you (and others) did
- CVS and implied arguments
- Committing
- Revision numbers
- Detecting and resolving conflicts
- Finding out who did what (browsing log messages)
- Examining and reverting changes
- Other useful CVS commands
- Adding files
- CVS and binary files
- Removing files
- Removing directories
- Renaming files and directories
- Avoiding option fatigue
- Getting snapshots (dates and tagging)
- Acceptable date formats
- Marking a moment in time
- Finding out more
CVS for Users 2: Branching/Merging/Watches
- Working with branches
- Branching basics
- Merging changes
- Creating a tag or a branch without a working copy
- The Dovetail approach - merging in and out of the trunk
- The Flying Fish approach - a simpler way to do it
- Branches and keyword expansion - natural enemies
- Tracking third-party sources (vendor branches)
- Exporting for public distribution
- Advanced CVS
- Log messages and commit emails
- Changing a log message after a commit
- Getting rid of a working copy
- History - a summary of repository activity
- Annotations - a detailed view of project activity
- Annotations and branches
- Using keyword expansion
- Watches
WinCVS for Users
- Checking out a working copy
- Finding out what you (and others) did
—
update and diff
- Committing
- Detecting and resolving conflicts
- Adding files
- Adding directories
- Removing files
- Removing directories
- Renaming files and directories
- Marking a moment in time (tags)
- Branches
TortoiseCVS for Users
- Checking out a working copy
- Finding out what you (and others) did
—
update and diff
- Committing
- Detecting and resolving conflicts
- Adding files
- Adding directories
- Removing files
- Removing directories
- Renaming files and directories
- Marking a moment in time (tags)
- Branches
|
CVS Server for Administrators
- Repository Administration
- Starting a repository
- Starting a new project
- The password-authenticating server
- Anonymous access
- Repository structure
- RCS format
- What happens when you remove a file
- The CVSROOT/ administrative directory
- Commit emails
- Controlling commits
- Other CVSROOT/ files
- Tips and troubleshoooting
CVSNT Server for Administrators
- Repository Administration
- Starting a repository
- Starting a new project
- The password-authenticating server
- cvs passwd
- Anonymous access
- Repository structure
- RCS format
- What happens when you remove a file
- The CVSROOT/ administrative directory
- Commit emails
- Controlling commits
- Other CVSROOT/ files
- Tips and troubleshoooting
CVS and Subversion Compared (conversion course)
- Overview
- User commands
- Revision numbering
- Tagging
- Branching
- Watches
- Repository remote access protocols
- Repository format
- Converting to Subversion
- Converting to CVS
|