Hi Vss2Svn! > Your patch essentially seems to be a much better approach to what I was > originally trying to do as a post-processing task with my filterorphans.cpp.
I saw your filterorphans.cpp but since I am no C expert at all, I didn't look to deeply into the source so I can't tell what it really does. But it seemed to me like something like it could/should be directly in the vss2svn script. > There were two basic classes of orphan I encountered: > a) 'false' orphans, where the vss2svn script had got confused, and was > treating something as an orphan despite its parent still being alive and > well (mainly due to confusing sets of moves / shares / etc.) Luckily something like that didn't exist in our database, because moves/shares were never done except in the case I described (share & destroy original). So I didn't encounter any of these. > classify these within the orphaned folder... i.e. rather than > orphaned/_CAAAAAAA/DongleCheck.cpp > orphaned/_DAAAAAAA/DongleCheck.dsp > orphaned/_EAAAAAAA/DongleCheck.h > ... etc. > This became > 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! > This classification is, as far as I can tell, something that can only be > done manually [...] 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. But I compiled a list of all orphans, classified them and put that into ActionHandler.pm and ran the script again. This time it gave me 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! > Navigating this orphaned folder or tracking anything that occured > within it is, to all intents and purposes, impractical (although the > head revision of the trunk does indeed match the sourcesafe version > :) ) Hehe, yes, that's true! I got a lot of orphaned stuff. Throwing out unwanted projects got rid of quite a few of them. And indeed, the head revision of trunk was a 100% match every time! Cheers, Ingo =;-> _______________________________________________ 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
