This is an antipattern and telling git to stop helping. One way that people have gotten rid of this warning is to turn off autocrlf. But it will come up again because you technically haven't fixed the problem. So, if the file is really a text file, you can safely ignore this warning. If you do nothing, the automatic conversion will happen the next time I, for whatever reason, modify the file in the working directory. Maybe you didn't want this so, for now, I've left the file in its original state in your working directory so that you can take the appropriate action, if any. If I ( git) store this like any other text file, which I'm doing, the next time you check out this file, it will have new line endings and thus will technically be different. Warning: this file is using different line endings ( LF) than expected ( CRLF) for the current system. The warning might be more clearly worded as: The commonly set option, that I think you already have enabled (check with git config tocrlf) will warn you about such files.
MAC UTILITY TO CONVERT LF TO CRLF WINDOWS
Of course, it does the same, in reverse, when going the other direction (creating a commit) so that diffs are consistent.īut, sometimes, programs on Windows machines write text files using Linux's line ending style. This means, on Windows machines, when checking out a working directory, for text files, git would automatically and silently convert all Linux's style line endings into Windows's style. Git decided to, by default, to use Linux's style on all the "official" versions of the code. Since git works on all modern platforms, and mostly manages code, which is mostly text files, it needs to gracefully handle this conflict that can happen when moving between OSes. Apple originally decided to make CR mean both, but they abandoned this when they moved to OS X and are today consistent with Linux. Linux decided to make LF mean to do both as it's very rare to want to just move the cursor down one line, and not go back to start, and there are other ways of doing that if needed.
Windows kept this meaning and thus needs two characters to "correctly" print a new line in a text file on the screen. Line Feed means advance the paper by one line. Carriage Return means to move the "carriage" (where you're typing), back to the beginning of the line. These come from the ancestors of keyboards: typewriters. Or, more precisely, have slightly different meanings for the text bytes CR and LF. For historical reasons, different OSes use different "line endings".
0 kommentar(er)
