Just saving random notes...

CVS

Importing a new project into CVS

From within the top level directory of the project you want to import:

cvs import -m 'Initial import into CVS' control control IBIS_20071113

parameters are:

-m {commit message}

Module name

Vendor branch

Vendor tag

It’s probably important to get the –k keyword expansion right too. You need to ensure the CVS server has the right ‘cvswrappers’ settings to identify binary files.

Watch out as the vendor branch becomes the head until you commit changes. A problem with this is you’ll get the vendor branch checked out and that’s what tags and branches will be created from. A workaround for this is to explicitly switch to the 1.1 revision of every file (which is guaranteed to exist, as the first revision number), and branch/tag from there.

Empty directories are not imported.

Checking out into a directory named other than the module name

cvs co -d devtwo control

This needs to be done from the parent directory.