Hi,
we try to reconstruct the correct flow of events with the converter. VSS
does not have a concept of repository wide revisions or atomic commits.
It will stores all changes to the items in the database in singualer
files. Fi you purge projects you will loose important glue in between
these singular files. In a very simple scenario, you create a file,
perform some modifications on it, share it to some other folder and
later purge the source folder. Since the information about the source
folder, esp. the initial creation of the file is lost, we will see
commits to the file before it actually came into live in the share
folder. From another perspective: we have purged the information of the
source folder. So we do not know the state of the source folder anymore.
We do not know that the source folder contained our specific file. But
we will see commits to the file. Later we see, that the file was shared
from somewhere into a new project. Again, we only now, that it was
shared from somewhere, but the source folder was purged.
In this case we use the oprhaned cache: This cache will hold old
activities on files, that doesn't have a parent at the time, where the
activity happend. Later, if the file is shared somewhere, we can move
the file out of the orphaned cache into the new place. But this is a
very recent addition, which is not in the source code, yet. You could
wait a few days, or you can try the patch yourself, if you check this
post
http://lists.pumacode.org/pipermail/vss2svn-users-lists.pumacode.org/2007-February/001005.html
Dirk
Strahovsky, Ido schrieb:
Hi,
Can you please explain what is the scenario that caused a file to be
placed in the "orphaned directory" ?
I migrated VSS DB of ~1GB and got almost 200MB of orphaned, although the
migration was very successful (I compared the output to the VSS FS by
Beyond compare and it was 100% identical).
Is there a way to get rid of the orphaned (not by svn delete, but to
remove it from DB) ? I tried to exclude it by svndumpfilter - but it
fails all the time.
Is there a way to avoid orphaned from being created ?
Thanks a lot,
Ido
_______________________________________________
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
_______________________________________________
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
