- cvs admin -kb <filename> (which will change the format of the file) and then you
- update
- copy the file that works
- commit
and perhaps the best place for this question is [EMAIL PROTECTED] (?), but here should be OK too i believe.
Best regards
Björn Carlsson
VersionSupport.com ready to help you
Daniel Bron wrote:
----- The attached message is an automatically ----- generated copy of mail delivered to [EMAIL PROTECTED]
Hello, A few months ago I mistakenly committed a Crystal Report (*.rpt) file into CVS as an ASCII file. This broke the file, but no one noticed for a while. Recently, I realized my error and tried to correct it by removing the file from CVS, then re-committing it as binary. 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. All our other *.rpt files work properly, because we reconfigured CVS to treat these files as binary by default. 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. Thanks, -D. Bron PS: If this is the wrong forum to make this inquiry, please forgive me, and direct me to the proper venue. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
