Spiro Trikaliotis wrote:

Hello,



Hi !
...


If you have so much fear about binary files, why don't you put * -kb
into your cvswrappers, and declare any text file explicitly? This way,
you cannot miss the binary files.



Actually, that was suggested 3 years ago as well. It turns out to be a very good one. However, while there are fewer standard file extensions that are text, many ad-hoc files (non-standard extensions) are almost allways text. Hence, it's easier to predict binary extensions that it is text extensions !


A suggestion 3 years ago was to run the "file" command on newly added files to determine it's format. That practice would solve your issue I presume.

While you may be right about ".doc" or ".au" files, in practice, I have found that this has worked remarkably well. Over the course of 3 years, I have never had anyone complain about files that CVS broke.

Almost all binary files added to CVS are - compressed source distros, prebuilt binaries, images, sound samples and open/win32 office files.

Anyhow, it works for me, YMMV !






_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs

Reply via email to