![]() The file will have its original line endings in your (current) working directory.Īs mentioned in git-for-windows/git issue 1242: Warning: (If you check it out/or clone to another folder with your current tocrlf configuration,) LF will be replaced by CRLF repoĪs mentioned in XiaoPeng's answer, that warning is the same as: Use this setting if you want to have CRLF line endings in your working directory even though the repository does not have normalized line endings.Īs described in " git replacing LF with CRLF", it should only occur on checkout (not commit), with tocrlf=true. No: you are on Windows, and the git config help page does mention ![]() Windows git "LF will be replaced by CRLF" Note: the warning message has changed with Git 2.37 (Q3 2022) gitattributes file and core.eol directives. That way, you avoid any automatic transformation, and can still specify them through a. ![]() Simply make sure that (as I recommend here): git config -global tocrlf false But that git config setting insists on changing those. Depending on the editor you are using, a text file with LF wouldn't necessary be saved with CRLF: recent editors can preserve eol style.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |