Hi,
vss2svn handles this by making it appear as if the file was being
modified in step each time. So, shares come out as distinct copies
that have the same history in SVN. This is how I read it in the wiki.
Since SVN does not support shares, the best solution is to refactor
your code as João said, but a workaround if needed is to share on a
directory level and use svn:external but then SVN operations become
more awkward than if there were no externals.
this is absolutly correct. vss2svn simply replicates all commits on all
shares in the same revision. There is no way to automatically detect
"recursive directory share" operations and to map them to an svn:exernal
property. One reason is that only file items are shared in VSS but
shared project items are created as new projects. That is, if you add a
file later to the share source, it will not automatically be added to
the share target.
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
