The only thing that I'd really like to retain are the labels, which is why
it would be great to get the ssphys.exe version of vss2svn working.  I was
looking at the ss.exe-based version however, and I could easily modify that
script to mimic the current status of the archive and generate the labels.
Have you tried to remove the time constraint in the SQL line in vss2svn.pl in function GetChildRecs

> AND (? - timestamp IN (0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25))

When you comment this line, you also need to remove the "timestamp" from the execute call

># $sth->execute( $parentdata, @{ $parentrec }{qw(physname actiontype timestamp author)} ); > $sth->execute( $parentdata, @{ $parentrec }{qw(physname actiontype author)} );

This will find all matching parent and child pairs, regardless of the time shift. The ADD action will finally happen at the timestamp of the child item.


On a quick side topic regarding the labels... our archive has labels that
contain the character '/' and when the label gets committed to the
Subversion repository it ends up creating labels that have subdirectories.
So that might be a potential issue to fix (with the obvious solution to
replace the '/' with another valid character).  Just a thought.  :-)

This should be easy to solve ;-)

Tbanks again for all of your assistance with this.  I really appreciate it.
You're welcome.

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

Reply via email to