Dusan Juhas writes: > > I used check_cvs utility and found several corrupted files in > the repository. > What I can do with a ,v file if cvs sais > cvs [checkout aborted]: premature end of change in .../bla.c,v > if I do cvs co -r x.y.z.w bla.c ?
First, figure out how the corruption happend and make sure it doesn't happen again. The most common cause is accessing the repository with NFS (or some other network file system), although hardware problems are also a possibility (especially if you're using cheap PC hardware with no error checking). You may be able to fix the file by getting an uncorrupted copy from a backup (you do back up your repository, don't you?), extracting each new revision that's in your current file and adding it to the backup copy (using RCS commands), and then replacing the corrupted file with the new file. Failing that, fixing a corrupted file is a black art -- you're going to have to become intimately familiar with the RCS file format and dig in with a text editor and whatever you can reconstruct of the file's history. -Larry Jones I think your train of thought is a runaway. -- Calvin's Mom _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
