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.
Jason
João Gustavo wrote:
Hello,
I have a VSS project with a lot of files using the SHARE VSS concept.
I want to use vss2svn to migrate the project to Subversion, but I need
to know how vss2svn handles this issue. Could anyone help me? What do
you do with SHAREs?
Thanks,
_______________________________________________
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
