Now comes the difficult part. There is no reason, why label promotion don't work backwards. So you can assign a label to a version of a file prior to the time the label was assign to one of its parent projects. Now we are in trouble, since we will see the version label first and need to decide that this belongs to a specific project.
Replying to myself: The above szenario will cause a problem, even in the proposed solution. Since the assigned version label has a data prior to the project label we will create this label first. Later we recognize the labeling of the parent project and copy the parentProject into the label directory, thereby overwriting the already existing label. The only solution is to collect all version Labels and in the last step copy them into the correct place.
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
