migrating from Vault to VSS

[hwaite]

I'm a timid guy thinking of migrating from VSS to Vault. Much like with women, I don't wanna commit. There are a lot of revision control packages out there and I'd like to play the field. Ideally, my experimentation could take place in the context of my current project. In order to stem data loss, I'd need to be able to propagate histories from one tool to the next, I'm aware that SourceSafe data can be moved to Vault, but what about the other way around? Better yet, anyone know of a sort of directed graph indicating which conversions are possible between various revision control apps? I recognize that Vault and VSS don't have identical feature sets. Perhaps a reverse migration would be possible only if I refrain from using certain functionality?

Hollis
"Aww, gee. You hear that? If we leave we can't come back." -Carl Burnett

[lbauer]

Much like with women, I don't wanna commit.

We don't have an export tool for VSS. After they've tried Vault, users generally want to settle down into a permanent relationship. If you want to just "date" Vault, I'd suggest testing in a non-production environment until you decide whether or not to commit.