I hear you. Cvs add/commit would take a long time and we'd have to script a recursice add/commit on so many files. Import seems simpler and we are happy to have this directory added as a new module.
But I am no expert so if I need schooling, by all means school away. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yves Dorfsman Sent: Tuesday, September 23, 2008 9:13 AM To: [email protected] Subject: Re: Import large amount of files on Windows (but cvsnt has issues) Wurdock, Tom wrote: > I have 450,000 files in a folder that need to be imported into cvs. > The server is linux. We're migrating from another source control system. > > The files were developed on Windows and have windows eol's. When I > try to import anything "cvs import" I get a bad error: > > cvs [import aborted]: received abort signal > cvs: /usr/local/src/cvs-1.11.21-v3/src/import.c:610: > process_import_file: Assertion `entdata->options[0] == '-' && > entdata->options[1] == 'k'' failed. > > That's not even the 450,000 files. Googling has not explained that > error. Not helping with the error, but thought I'd ask anyway. Do you understand the difference between "cvs add" then "cvs commit", and "cvs import" ? It might not be the case for you, but I have found that a lot of beginner run a "cvs import" when really they simply want to "add" their files to the repository. -- Yves. http://www.sollers.ca/blog/2007/GA-M57SLI-S4_hangs_on_boot
