That leaves me with 3 files with differing content. Now I'll
investigate those to see why VSS and vss2svn come up with different
results.
Great! Let us know what you find.
This sounds good.
Please check the following: If you delete a file in vss the file is
still "alive" and take part in check ins via one of it's shares. If you
recover the file later, you will recover it to a newer version. The
converter currently will delete files and recover them from the last
known revision. So after the recovery the file is in the state, when it
was deleted.
In order to solve this, we must move files that are deleted into an
_deleted subfolder, so that the files can take place in commits. A
recover will move the file back.
On the other hand, I'm not sure, whether I consider this as a bug in vss
and that I don't want to solve this issue ;-)
Dirk
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
