The Source Integrity Professional Edition User Guide - MKS

Using Existing
RCS Archives
Example
The command
vss2rcs $/proj1/proj2/file1
Importing Files
converts the Visual SourceSafe archive file1 from the project
$/proj1/proj2 and places the resulting Source Integrity working file
in the current directory. The corresponding archive is placed in a
location determined by the value of the RCSPATH configuration
variable.
Similarly,
vss2rcs -s $/proj1/proj2 file1 file2
converts the Visual SourceSafe archives file1 and file2 and places
the resulting working files in the current directory.
With the -a option, you can have the Source Integrity working files
created in a location other the current directory. For example,
vss2rcs -a c:/temp $/proj1/file1 $/proj1/file2
places the working files created from the Visual SourceSafe archives
$/proj1/file1 and $/proj2/file2 in the c:/temp directory.
Source Integrity accepts traditional RCS archives without conversion.
Source Integrity will, however, begin to add proprietary information
to the archives to accommodate its specialized functionality.
Source Integrity provides the configuration option VanillaRCS to
allow compatibility with traditional RCS. When VanillaRCS is set in
a project, or in your Personal Configuration, any new archives
created will be made RCS-compatible.
Note Other RCS systems, such as GNU RCS, are not able to take
advantage of Source Integrity project information.
User Guide 151