imajeff wrote on Saturday, December 16, 2006:
Is Richard keeping FreeRTOS in Subversion now? I remember some consideration long ago. If so, I’m assuming the source code is stored as binary instead of text/plain, because of the following errors.
I have just tried importing the latest (4.1.3) to my svn repository using auto-props. The problem is that it does not try to guess when finding a text file with mixed newline formats, and stops the importing process.
It is easy enough to fix once I find each file (the tedious part is finding each file, and what format it should be). I convert it using utilities `dos2unix` or `unix2dos`.
For anyone wondering what this “newline” problem is all about, I’ll explain: SVN can distinguish ASCII text files from binary (using extensions such as .c or .h), and store text files in a universal form. The advantage is that when anyone checks out files, the source will be converted automatically to the standard newline form for the OS. The developer can then easily view/modify any files without the limitations I’ve had to continually deal with.
To describe the problems found, I use these terms:
DOS text format line ends shown "\r\n" meaning [CR LF]
UNIX text format line ends shown "\n" meaning [LF]
svn: File ‘FreeRTOS/Demo/lwIP_MCF5235_GCC/web.h’ has inconsistent newlines
- This file has an orphan ‘\r’ mid-line, the rest DOS format
000006f0 “\n#endif /* \r */\n\n” [EOF]
svn: File ‘FreeRTOS/Demo/MicroBlaze/main.c’ has inconsistent newlines
- This has one ‘\n’ by itself, the rest DOS format
0001b00 “\r\n \treturn 0;\n}\r\n/*-----------”
svn: File ‘FreeRTOS/Demo/uIP_Demo_IAR_ARM7/uip/fsdata.c’ has inconsistent newlines
svn: File ‘FreeRTOS/Demo/CORTEX_LM3S102_KEIL/include/pdc.c’ has inconsistent newlines
- These end with “\r\n”, the rest UNIX format “\n”
svn: File ‘FreeRTOS/Source/portable/MPLAB/PIC18F/port.c’ has inconsistent newlines
- This had “\r\n\n” which I converted to “\r\n\r\n”
