I'm not sure; git handles all files as binary data, so it depends on how RCS handles EOL.
You mean it has no EOL handling at all? With subversion, you get files where the EOL convention does not matter (such as most source files) converted to the local EOL convention when checking out, and then back again when committing. This is conventient for example for some source files which make sense to edit on W*ndows (because they contain W*ndows-specific code, and thus need to be tested in that environment). In CVS, those files had CRLF convention in the repository, which is inconventient when checking out on a non-W*ndows system.
Furthermore, a specific EOL convention can be enforced for a file; but I guess that can be emulated with commit hooks. (I assume git has _those_ at least...)