<br><font size=2 face="sans-serif">On Wed, 02 Oct 2002 16:25:47 GMT, tmh@nodomain.org (Tony Hoyle) wrote:</font>
<br><font size=2 face="sans-serif">> </font>
<br><font size=2 face="sans-serif">> By definition, modifying a binary file is has undefined behaviour, so</font>
<br><font size=2 face="sans-serif">> it's not a good idea. 99% of the time if you do this you will end up</font>
<br><font size=2 face="sans-serif">> with a broken file. 'Revision' for example is something that is only</font>
<br><font size=2 face="sans-serif">> going to be seen in text file (although there is a finite chance if it</font>
<br><font size=2 face="sans-serif">> appearing, for example in a .gif file). Binary files tend to be</font>
<br><font size=2 face="sans-serif">> executables (can't change them), word documents (can't change them)</font>
<br><font size=2 face="sans-serif">> and other things you don't want to mess around with.</font>
<br><font size=2 face="sans-serif">> </font>
<br><font size=2 face="sans-serif">> Tony</font>
<br>
<br><font size=2 face="sans-serif">Of course by default, for all binary files it is not possible, but there are files which the user (me :)) would like to handle as binaries (because otherwise CVS will change the newline characters) with still using the keyword substitution with the fixed way I described before.</font>
<br><font size=2 face="sans-serif">It means that he is sure if the keyword appears in the file, that should be substituted. A good example is Oracle D2K Forms .FMBs or .PLLs (MMBs...), where I cannot use this feature at all now.</font>
<br>
<br><font size=2 face="sans-serif">It could be the decision of the user (with using the new switch, possibly in cvswrappers).</font>