Dirk wrote:
> Ref the branch handler... ideally, when (say) BAAAAAAA is branched at
> revision 3 to create GAAAAAAA, the internal state tracking GAAAAAAA's
> parent paths would inherit BAAAAAAA's up to revision 3. Then if
> GAAAAAAA is shared elsewhere and then branched or pinned to revision 1
> or 2, it knows where to get this...
Should be fixed in [298]. The code will query the ancestor for a valid
path and the copy from that one.
I've still not tried this but had a quick look at the code changes...
The following line added to Dumpfile.pm may be of concern:
$gVersion{$data->{physname}} = $gVersion{$data->{info}};
Would this copy the gVersion information for versions beyond the branch
point as well as before it?
i.e. if development continues on the trunk to (say) revision 5, then a
branch is created at (say) revison 3 from the V1.0 label to create a
maintenance version, or a "rollback" operation occurs. The new physical
file (which starts life at revision 3) should not inherit any
information from the original file's revisions 4 or 5, if this could
interfere with further checkins on the branch.
--
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
