Oops ... I forgot to attach the file.
Here it is ...
As an attachment there is the source code for my vssls utility.
I started it month ago but did not find the time to do the analysis
further.
Maybe someone can make use of it ...
Going into one of those a, b, c, ... directories of VSS (maybe mounted
using Samba or just copied to Unix) you can use vssls to show what files
are in this directory.
Maybe someone else has analysed VSS structure and can give further
information, too?
"David L. Martin" wrote:
> Laine,
>
> >Speaking of converting to CVS from other systems - has anyone ever
> >converted a Visual SourceSafe repo into CVS? If so, do you have a script
> >laying around? I've convinced "the powers" that we need to switch from
> >VSS to CVS, but we've got several years worth of VSS history and I'd
> >much prefer to retain it in the switch. (Said "powers" don't see any
> >advantage to doing this, but I know from experience how useful things
> >like cvs annotate are.)
> >
>
> For a circuitous path to do this, if you have a recent version of PVCS
> Version Manager (6.6 is the latest), it comes with a conversion script to go
> from VSS to PVCS (although I've never used it). You could then run the
> pvcs2cvs.pl conversion script (which I have used) to go from PVCS to CVS. I
> don't know of a direct conversion script from VSS to CVS, however.
>
> David
--
Heiko Nardmann (Dipl.-Ing.), [EMAIL PROTECTED], Software Development
secunet Security Networks AG - Sicherheit in Netzwerken
(www.secunet.de),
Weidenauer Str. 223-225, D-57076 Siegen
Tel. : +49 271 48950-13, Fax : +49 271 48950-50
vssls.cpp
