Hi,
last weekend I thought about correctly handling renames in the case of
pinned shares. VSS performs renames on every share of the item,
regardless whether it is pinned or not. We used the share+pin method to
generate our release maintenance folders and labeled the releases. So if
a rename is done on the original tip project, the release projects are
broken, since the pinned shares are renamed also. My understanding of a
pin is, that it pins the file into the state that it had while it was
pinned. This includes the name and not only the content. For the
conversion it wouldn't be any problem to omit renames on pinned shares.
But this will brake the comparability of the subversion archive and the
last version in VSS after the conversion. So I'm thinking of a flag to
tell vss2svn to do it the correct way. Any ideas on this?
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
