On Tue, Jan 08, 2008 at 08:07:15AM -0500, Peter Harris wrote: > > Actually, Subversion does the Right Thing, and treats everything as a > binary file until and unless you explicitly set the svn:eol-style > property on each file that you want it to mangle. Not exactly. Actually, Subversion detects binary or text file based on heuristic. http://subversion.tigris.org/faq.html#binary-files But the status of a file as binary or text has no effect whatsoever on on CRLF conversation, which is controlled by another property. By default, most of your text files will be detected as text (unless you use non-ASCII character like Cyrillic), but they will not have CRLF conversation. Now, you have to set svn:eol-style=native for each new file, which of course can be done automatically based on file extension, but that should be configured by each user in his or her global config file. Obviously, it does not work well for cross-platform projects, because many users forget to set svn:eol-style=native for some extensions. Moreover, the issue tends to repeat itself for every newly introduced file extension... IMHO, having the binary or text status completely independent from CRLF conversation is insanity... Dmitry - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
