Tim,
I have modified the diff a little, so it's not identical to what you have. The way it behaves for me is:
1. applies cleanly to DOS version 2. applies OK to float-only version(s) with messages about offset lines (expected) 3. applies cleanly to Linux if the cr/lf are fixed.
This raises the question of how we handle newlines in CVS. Unless CVS has a way to fix newlines on-the-fly, we probably need to adopt the Linux newline standard for files and dif's (or the other, the point is to choose). As long as we package everything with zip, unpacking with the zip -a option will fix newlines for the local system.
Yes, CVS handles newlines on-the-fly. If you have them there under Linux, as happens with certain files in my Allegro experimental source, it complains and won't put the files in the repository. So, I'll need to clean up the Allegro source before I can put it in CVS. It occurred to me the other day that if I combined your patch with mine, I wouldn't have to figure out how to back changes out of CVS, put in your patch, and then put my changes back in. I am now back home. No more travelling. At least not until I get a job. Jonathan