I'm finding that the "parent record" for a branched file is not getting
added to the PhysicalAction table. There appear to be some branch
operations that encode the branch in a BranchToFile element at the same
level as Version elements instead of as Action sub-elements. Here's an
example:
<Version offset="92530">
<Action ActionId="CheckedIn">
<Offset>92310</Offset>
<CheckInSpec>$/Top/Source/Main</CheckInSpec>
</Action>
<Date>1065027863</Date>
<UserName>Swdev</UserName>
<VersionNumber>91</VersionNumber>
</Version>
<Comment offset="92942"></Comment>
<BranchFile offset="92951">
<BranchToPhys>XSTAAAAA</BranchToPhys>
<PreviousOffset>87022</PreviousOffset>
</BranchFile>
<FileDelta offset="92975" />
(A version element follows this.)
The first Version element of the matching XSTAAAAA is a Rollback, which one
would expect from a branched file.
I'm figuring the BranchFile element has no datestamp so it's inferred from
the child file, and matching by timestamp can at best be done by verifying
that it's between the datestamps of neighboring Version elements.
_______________________________________________
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
