Dirk: How does this tie into the RestoreProject action? I'm using 0.11
and I've got a ton of orphaned directories in the result... the
migration complains about unrecognized RestoreProject actions in the VSS
archive. I think the original maintainer of my VSS database used
Archive/Restore on the Project-level liberally to move directories
around.
Hi,
I'm still working on this, but havn't made any major progress. I havn't
tried to "Archive" and "Restore" projects in order to move things
around. But I would expect, that (even when we have correct support for
archive/restore cycles) you will get a lot of orphans in the first
place, until the project is restored into the new place.
Archiving a project is like saving all physical information into a file
and then destroy the data.
Restoring is like extract all saved information into a new place,
thereby fixing possible naming conflicts of physical file names but
don't care about time.
So if you have archived a project and you create a new project to
restore into, the new project will have a creation time later than any
file in the archive. All converted files will live in the orphaned space
until they are restored into the new location. This will be handled as a
move action.
Currently the Archive/Restore actions are broken, since I have very less
experience with it. I'm just learning ;-)
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
