Hello, I've discovered a pitfall with moving files as explained in the CVS manual and info. It happens when you're trying to move a binary file which is not a type listed in cvswrappers. If you do the following procedure, everything is a-ok: cvs add -kb binary_file.xxx; cvs commit mv binary_file.xxx binary_file.yyy; cvs rm binary_file.xxx; cvs add -kb binary_file.yyy cvs commit binary_file.xxx binary_file.yyy cvs log binary_file.yyy -> keywords still set to binary but lost latest version number. If you do the following to preserve the revision number during the process, you will not have a binary file anymore: cvs add -kb binary_file.xxx; cvs commit mv binary_file.xxx binary_file.yyy; cvs rm binary_file.xxx; cvs add -kb binary_file.yyy cvs commit -r 3.3 binary_file.xxx binary_file.yyy cvs log binary_file.yyy -> keywords still set to expansion Uh Oh! However, if you do it in two stages, all is fine. cvs add -kb binary_file.xxx; cvs commit mv binary_file.xxx binary_file.yyy; cvs rm binary_file.xxx; cvs add -kb binary_file.yyy cvs commit binary_file.xxx binary_file.yyy cvs commit -r 3.3 binary_file.yyy cvs log binary_file.yyy -> keywords still set to binary and version number okay. Note that if the file extension matches the binary extensions listed in CVSWRAPPERS then the second procedure works fine. If this is a feature, perhaps this needs to be explained in the CVS manual/info section on moving files safely. _______________________________________________ Bug-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-cvs
