Ingo Schmidt wrote:
> orphaned/DongleCheck/DongleCheck.cpp
> orphaned/DongleCheck/DongleCheck.dsp
> orphaned/DongleCheck/DongleCheck.h
Exactly! If you find out where these files once really were, I think
it is safe to do this!
The point I was making was that by keeping them in (better classified)
subfolders of orphaned, this avoids conflicting with the proper head
revision, and effectively resurrecting projects that had been deleted.
Any files that are missing from the head revision without doing this
would be "false orphans"...
Yes, this is what I did! I had vss2svn convert the whole database,
then looked in the files it created and checked that in the VSS
history. This is a tedious job and if you want to be on the safe side,
you have to do it manually, I guess.
I also cross-referenced this against the
_vss2svn\datacache.PhysicalAction.tmp.txt file (imported into Excel and
sorted on the timestamp column). This way you can pull out a whole batch
of files that were added together and put the mapping from all these
physical names to a new folder.
all the pretty names and it also took care of creating all the
folder levels. That's why I liked my idea so much:
No messing with the (HUGE!!) dumpfiles!
Indeed... and much of the messing around in the cpp file was to deal with:
a) C being a terrible language for text processing
b) needing to fix-up things like creating (or suppressing creation of)
folders.
If I decide to bother classifying the orphans again, I'll almost
certainly do it similar to your way rather than trying to fix up
filterorphan.cpp
--
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
