Dirk wrote:
Ok, the problem is, that you managed to add a subproject to a project at
exactly the same timestamp as you added the project to its parent
project.
To add a quick observation... from a brief glance it appears that the
IDs are in the "wrong" sequence?
According to the normal ID sequence used for physical files, EDADAAAA
would imply a physical file allocated earlier than TUADAAAA (as D is
before U). Since vss2svn uses this ID reversed as a sort key to
disambiguate items with the same timestamp, this would be why the
actions get reversed.
Ideally I guess it wants some form of sort key that will guarantee that
a child item sorts after its parent, but I can't see how to do that at a
point where the full parent path is not known.
--
Stephen Lee <[EMAIL PROTECTED]>
Software Engineer, Vision Group - Pro-Measure Leader
Wilcox Associates Inc. (U.K.)
_______________________________________________
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
