Hello Daniel, * On Thu, Mar 04, 2004 at 01:41:18PM -0500 Daniel Bron wrote: > It appears, however, that CVS remembers the original version of the > file was ASCII, and is treating the new version as ASCII, even though > I explicitly uploaded it as binary. This is manifest in the fact that > the report is still broken. [...] > Is there any way to get CVS to treat this report as binary? [...] > I'm using WinCVS 1.3.13.2 Beta 13 (Build 2) on Windows 2000, service > pack 3, connecting to CVSNT 2.0.11, on another Win2Ksp3 machine.
I don't know about WinCVS, but with CVS, I would do cvs admin -kb <filename> As the cederqvist tells us about the treatment of binary files (in section 9.2 "How to store binary files"): However, in using cvs admin -k to change the keyword expansion, be aware that the keyword expansion mode is not version controlled. This means that, for example, that if you have a text file in old released, and a binary file with the same name in new releases, CVS provides no way to check out the file in text or binary mode depending on what version you are checking out. There is no good workaround for this problem. HTH, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
