I've been asked to migrate our CVS repository over to Subversion (hope that's not a dirty word here). While running the cvs2svn tool, I got a list of a dozen or so files with the error "<filename> is not a valid ,v file". These files are unrelated and obsolete (most have been abandoned or are in the Attic already), so losing them completely is not a concern.

There are several modules in the repository, but none that cover all of the affected files.

What would be the best way to deal with these files? I'm no CVS expert, so maybe I'm missing the obvious easy answer...

Option 1 - Manually delete the files from the folders in the repository from the shell.
Option 2 - Create a new module that covers all of the files, attempt to check them out and recommit them in the hopes it'll fix the corrupted files?
Option 3 - Run a sanity checking application that I've yet to find :)


Thanks in advance for any advice you all could give...


-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.7.1 - Release Date: 3/9/2005


-- This message has been scanned for viruses and dangerous content, and is believed to be clean.



_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/info-cvs

Reply via email to