quite often a file will be created as orphaned and then moved to the proper location. this is primarily due to how VSS stores the files that have been moved into the repro rather than created in it directly. Also, be sure you are using the latest nightly build as many issues have been fixed regarding orphaned files.
Bryan On Tue, Oct 7, 2008 at 8:45 AM, Matt Mannix <[EMAIL PROTECTED]> wrote: > Good Morning, > > Today I have run into an odd issue which leads me to beleive I must be > doing something incorrect. I was given a folder containing a VSS rep > about 4.5G in side. using vss2svn I created a dump file successfully > from the VSS repo. I then created a svn repo with the svnadmin command > to old the dump file and ran "svnadmin load foo < foo.dumpfile". > > Does anyone know what might cause every file in the VSS repo to be > considered orphaned? Maybe there is something significantly wrong with > the repo I was provided or I have overlooked an important step in the > import process? > > -- > ~matt > > _______________________________________________ > 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
