While writing these lines, I had an idea of an easy solution for
this. Currently I'm using "99999999" as the physical id for the dummy
project. Since we are not dependent on the length of the physical ID,
I could use the id of the orphaned physical file together with a
magic marker for orphaned files. In case someone is asking for the
item path of such an item, we would stop at the magic marker and
return a complex directory, containing the orphaned folder and the
physical name of the orphaned file, here. All missing directory
creates are picked up by the sanity checker, so there shouldn't be
any problem. I will give this a try directly.
I gave this a fast try and just committed the little modification. If
you have time, it would be wonderful if you could test it. The code
uses an underscore as the magic marker, so for an orphaned item
"file.txt" you will now see, e.g.:
/orphaned/_HAAAAAAA/file.txt
Hope this helps to prevent the double filename issue.
Arrgh, forgot to mention, that you can resume from BUILDACTIONHIST
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
