Paul Coene writes:
>
> 1) I had a very large (1000+ files) project that I needed to get into
> CVS. I noticed that you need to tell CVS whether a file is binary or
> not. I didn't want to have to do this file by file, so I ran the
> entire import with the -kb flag. Was this ok, or are all my checkout
> commits going to make full copies instead of diffs since all files
> were imported with the binary flag? Was there a better way?
No, it isn't OK. CVS always does diffs, even on binary files, so that
isn't a concern, but CVS won't automatically merge binary files and the
line endings in the repository may be messed up such that if you check
out on a platform with different line ending conventions, the files will
be incorrect.
How bad it is depends on whether your (client, if you're using
client/server CVS) system distinguishes between text and binary files
(Unix and Linux do not, Windows does). If not, then the data in the
repository is fine, you just need to fix the keyword expansion mode for
the non-binary file: do ``cvs admin -kkv'' on all the text files and
then ``cvs update -A'' to fix the working directory copies.
Have you committed the changes? If not, you can just do ``cvs update
-C'' in your working directory to throw away all the changes. If you
have committed changes and now want to revert them, you can do a reverse
merge to undo the changes and then commit the files:
cvs update -j BASE -j REV_YOU_WANT
cvs commit -m'Revert to REV_YOU_WANT'