 |
 |
On Wed, 13 Jun 2007, Peter W. Draper wrote: > On Tue, 12 Jun 2007, Tim Jenness wrote: > >> On Mon, 11 Jun 2007, Tim Jenness wrote: >> >>> One thing that we do need to check is that all binary files are marked with >>> the binary flag. I'll try to check this on Friday but if anyone spots any >>> incorrectly flagged files please do a 'cvs admin -kb xxx' on them. >> >> Just gone through thirdparty and it's really odd: all the binary files >> are marked with -ko rather than -kb. -ko is problematic because whilst >> it disables keyword substituion it indicates that line endings can be >> changed. I've changed them to -kb and > >> I'm at a loss as to how they came to be -ko initially. > > That's simple to explain, I did it. When I import thirdparty sources I > always use -ko (and import the whole tree using that). Since that seems to > do the job I've never differentiated binary files. > Thanks. Didn't think to look at the ASCII files. I'm fixing up the -kb in the rest of the tree now (since I realise that I will still have to go through and do this even if some of the files have been fixed up since I can't tell which directories are complete) -- Tim Jenness JAC software http://www.jach.hawaii.edu/~timj