Disable automatic line endings conversion on windows
authorRaphael Marmier <raphael@marmier.net>
Mon, 03 Jul 2006 10:18:46 -0700
changeset 2550 45235e492cc6
parent 2549 e1831f06eef1
child 2551 764a54eb8c5a
Disable automatic line endings conversion on windows The rationale behind this is that such conversion implies a particular situation in which all files in the repo are terminated by only LF. This is documented nowhere and it bit me sharply when I upgraded. Furthermore, it works on the assumption that a file containing no NULL characters are actually a text file. Therefore it cannot guarantee that no binary file will be harmed in the process. Currently, if a file already contains CRLF line endings when it is copied to the working dir from the repo, then the version in the working dir will be corrupted by an extra CR. I'm working on a patch that will turn this into a warning. But as a side effect, committing such a file back will strip it from its CR. In all case, unrequested data modification can occur under the feet of the user, which is bad(tm), ihmo.
contrib/win32/mercurial.ini
--- a/contrib/win32/mercurial.ini
+++ b/contrib/win32/mercurial.ini
@@ -18,7 +18,8 @@ hgext.win32text =
 
 [encode]
 ; Encode files that don't contain NUL characters.
-** = cleverencode:
+
+; ** = cleverencode:
 
 ; Alternatively, you can explicitly specify each file extension that
 ; you want encoded (any you omit will be left untouched), like this:
@@ -28,7 +29,8 @@ hgext.win32text =
 
 [decode]
 ; Decode files that don't contain NUL characters.
-** = cleverdecode:
+
+; ** = cleverdecode:
 
 ; Alternatively, you can explicitly specify each file extension that
 ; you want decoded (any you omit will be left untouched), like this: