Hello Jason:
I've been watching the "Missing VSS ADD" thread, and I don't think I
reported this but not all of my files came through the final export
either, but for a different reason. I actually thought that it NEVER
came out, but that's not exactly true. I really don't know what
happened to this file but it is certainly interesting, and it seems to
have something to do with a rollback.
thanks for your comments. Actually the rollback record is the
corresponding action to a branch. If the file that you are "rolling
back" is not involved in any other share, then the rollback will simply
delete all versions. That means: If you have a simple, non shared file,
there is no problem with a rollback. You will not see any events in the
history after rolling back. On the other hand, if the file is shared,
the share will use the "younger revisions" hat you are trying to delete.
rolling back this file will silently branch the file in the background
at the version that you selected for the rollback activity. in order to
keep the share alive.
The problem seems to be, that this "automatic branch" is not recorded in
the parent. So there is no corresponding "branch" record. Rollback and
Branch records are norally merged together to find the necessary Parent
/ Child information . If we only have a "Rollback" record, I do't know
what will happen.
I have to investigate this further.
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
