blocks|key|2506103|text|在我设置core.autocrlf=true之后，我得到了"LF将被git+add替换“(注而不是"CRLF将被LF替换”)，当我正在git+adding时(或者可能是在git+commit上？)在设置core.autocrlf=true之前已签出的存储库(确实使用LF)上窗口中的编辑文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2506104|我用core.autocrlf=true做了一次新的检查，现在我没有收到这些消息。|2506105|entityMap^0|4|I|Y|7|1V|7|2D|A|2T|I|0|2|I|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|I|$]]

After I set <code>core.autocrlf=true</code> I was getting "LF will be replaced by CRLF" (note not "CRLF will be replaced by LF") when I was <code>git add</code>ing (or perhaps it was it on <code>git commit</code>?) edited files in windows on a repository (that does use LF) that was checked out before I set <code>core.autocrlf=true</code>.

I made a new checkout with <code>core.autocrlf=true</code> and now I'm not getting those messages.

blocks|key|2506113|text|做一件简单的事情：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2506114|打开git-集线器(Shell)并导航到属于的目录文件(cd+/a/b/c/.)|ordered-list-item|2506115|执行dos2unix+(有时是dos2unix.exe)|2506116|现在就开始吧。如果你再犯同样的错误。执行上述所有步骤，除了dos2unix之外，请执行unix2dox+(有时执行unix2dos.exe)|2506117|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|M|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|N|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|O|8|@]|9|@]|A|$]]]|J|$]]

Do just simple thing:
<ol>
<li>Open git-hub (Shell) and navigate to the directory file belongs to (cd /a/b/c/...)</li>
<li>Execute dos2unix (sometime dos2unix.exe) </li>
<li>Try commit now.
If you get same error again.
Perform all above steps except instead of dos2unix, do unix2dox (unix2dos.exe sometime) </li>
</ol>

blocks|key|2506162|text|是的，，，警告是向后的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2506163|事实上，这根本不应该是一种警告。因为所有这些警告都是说(但不幸的是向后)，文件中带有Windows行尾的CRLF字符将被LF‘saying替换。这意味着它被标准化为*nix和MacOS使用的相同行尾。|2506164|没有什么奇怪的事情发生，这正是你通常想要的行为。|2506165|它当前形式中的这个警告是两件事之一：|2506166|一个不幸的错误，再加上一个过于谨慎的警告信息，或者|ordered-list-item|2506167|一个很聪明的计划让你认真考虑一下.|2506168|;)|2506169|entityMap^0|3|1|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|Y|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|Z|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|10|8|@]|D|@]|E|$]]|$1|O|3|P|5|N|7|11|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|12|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|T|$]]

YES the warning is backwards.

And in fact it shouldn't even be a warning in the first place. Because all this warning is saying (but backwards unfortunately) is that the CRLF characters in your file with Windows line endings will be replaced with LF's on commit. Which means it's normalized to the same line endings used by *nix and MacOS. 

Nothing strange is going on, this is exactly the behavior you would normally want.

This warning in it's current form is one of two things:

<ol>
<li>An unfortunate bug combined with an over-cautious warning message,
or </li>
<li>A very clever plot to make you really think this through...</li>
</ol>

;)

blocks|key|1188551|text|所有这些都假设为core.autocrlf=true|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1188552|原始错误：|1188553|警告:+LF将被CRLF取代
该文件的原始行结束将在您的工作目录中。|blockquote|1188554|错误的内容应该是：|1188555|警告:+LF将被您的工作目录中的CRLF+替换。
该文件将在git存储库中有它原来的LF行结尾。|BOLD|1188556|解释这里|1188557|这种方便的转换的副作用，这就是你所看到的警告，就是如果你最初创作的文本文件有LF结尾而不是CRLF，它将像往常一样与LF一起存储，但是当稍后签出时它会有CRLF结尾。对于普通的文本文件，这通常是很好的。在本例中，警告是“供您参考”，但如果git错误地将二进制文件评估为文本文件，则这是一个重要的警告，因为git随后将破坏您的二进制文件。|1188558|基本上，以前是LF的本地文件现在将在本地拥有CRLF。|1188559|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1967370/git-replacing-lf-with-crlf/1967986#1967986^0|8|I|0|0|0|0|E|7|10|B|0|2|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|16|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|17|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|18|8|@]|D|@]|E|$]]|$1|M|3|N|5|J|7|19|8|@$9|1A|A|1B|B|O]|$9|1C|A|1D|B|O]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1E|8|@]|D|@$9|1F|A|1G|1|1H]]|E|$]]|$1|R|3|S|5|J|7|1I|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|1J|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|12]]]]

All of this assumes <code>core.autocrlf=true</code>

Original error:

<blockquote>
 warning: LF will be replaced by CRLF 
 The file will have its original line endings in your working directory. 
</blockquote>

What the error SHOULD read:

<blockquote>
 warning: LF will be replaced by CRLF in your working directory 
 The file will have its original LF line endings in the git repository 
</blockquote>

Explanation <a href="https://stackoverflow.com/questions/1967370/git-replacing-lf-with-crlf/1967986#1967986">here</a>:

<blockquote>
 The side-effect of this convenient conversion, and this is what the warning you're seeing is about, is that if a text file you authored originally had LF endings instead of CRLF, it will be stored with LF as usual, but when checked out later it will have CRLF endings. For normal text files this is usually just fine. The warning is a "for your information" in this case, but in case git incorrectly assesses a binary file to be a text file, it is an important warning because git would then be corrupting your binary file.
</blockquote>

Basically, a local file that was previously LF will now have CRLF locally

blocks|key|2506233|text|-7月9日最新情况|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2506234|删除@mgiuca评论中的“它是正确和准确的”|2506235|======|2506236|，NO，.它不是在谈论您当前使用CRLF的文件。取而代之的是使用LF来讨论文件。|offset|length|style|BOLD|CODE|2506237|它应改为：|2506238|警告：(如果您签出/或克隆到具有当前配置的另一个文件夹)，则LF将被CRLF替换
该文件将在您的(current)工作目录中有其原始行尾。|blockquote|2506239|这幅画应该能解释它的含义。|2506240|📷|atomic|2506241|​|2506242|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/ffb9cb0052eaf6499896308559ad6107.jpg|imageAlt^0|0|0|0|0|4|G|4|W|2|0|0|I|2|1D|7|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|19|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1A|8|@$H|1B|I|1C|J|K]|$H|1D|I|1E|J|L]|$H|1F|I|1G|J|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1H|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1I|8|@$H|1J|I|1K|J|K]|$H|1L|I|1M|J|K]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1N|8|@]|9|@]|A|$]]|$1|T|3|U|5|V|7|1O|8|@]|9|@$H|1P|I|1Q|1|1R]]|A|$]]|$1|W|3|X|5|6|7|1S|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15|16|-4]]]]

--Update on 9th July---
Removed &quot;It is correct and accurate&quot; as commented by @mgiuca
======
NO. It is NOT talking about your files currently with <code>CRLF</code>. It is instead talking about files with <code>LF</code>.
It should read:
<blockquote>
warning: (If you check it out/or clone to another folder with your current core.autocrlf configuration,)LF will be replaced by CRLF
The file will have its original line endings in your (current) working directory.
</blockquote>
This picture should explain what it means.
<a href="https://i.stack.imgur.com/ZXee5.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/ZXee5.jpg" alt="enter image description here" /></a>

blocks|key|109423|text|git+config+--global+core.autocrlf+false适用于全局设置。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|109424|但是，如果您正在使用Visual，则可能还需要为某些类型的项目(例如，.gitattributes类库应用程序)修改c#：|109425|删除线*+text=auto|unordered-list-item|109426|entityMap^0|0|13|0|Z|E|0|3|B|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|K|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|L|$]]

<code>git config --global core.autocrlf false</code> works well for global settings.

But if you are using Visual Studio, might also need to modify <code>.gitattributes</code> for some type of projects (e.g c# class library application):

<ul>
<li>remove line <code>* text=auto</code></li>
</ul>

blocks|key|2506281|text|我面临着类似的问题，在windows上使用vscode(v1.57)尝试了在其他答案中定义的解决方案，但没有奏效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2506282|因此，对我来说，以下步骤起了作用：|2506283|根文件夹中有一个名为.editorconfig的文件|ordered-list-item|2506284|打开此文件并使用end_of_line+=+lf更改end_of_line+=+crlf|offset|length|style|CODE|2506285|运行git+rm+--cached，警告消失！！|2506286|entityMap^0|0|0|0|8|G|Q|I|0|2|F|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|T|8|@$I|U|J|V|K|L]|$I|W|J|X|K|L]]|9|@]|A|$]]|$1|M|3|N|5|F|7|Y|8|@$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|P|$]]

I faced similar issue and using vscode(v1.57) on windows tried solutions defined in other answers but didn't worked.
So for me following steps worked:
<ol>
<li>In root folder there is a file named .editorconfig</li>
<li>open this file and change <code>end_of_line = lf</code> with <code>end_of_line = crlf</code></li>
<li>run <code>git rm --cached</code> and warning gone!!</li>
</ol>

blocks|key|2506310|text|确保在.gitignore文件中添加了不必要的文件或文件夹。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2506311|例如node_modules|2506312|如果仍然要面对，那么运行以下命令|2506313|git配置--全局core.autocrlf+false``|2506314|entityMap^0|3|A|0|2|C|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|U|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|M|$]]

Make sure you added unnecessary files or folders in <code>.gitignore</code> file.
e.g.
<code>node_modules</code>
if still face then run this command
``git config --global core.autocrlf false```

blocks|key|109477|text|这是因为Windows上的GitHub桌面配置假定CRLF，但文本编辑器可能使用LF。您可以更改本地存储库设置，改为使用lf。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|109478|导航到git的根，并按完全相同的顺序执行此操作。|109479|git+config+core.eol+lf
git+config+core.autocrlf+input|code-block|syntax|javascript|109480|资料来源:+GitHub问题|109481|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/desktop/desktop/issues/3841#issuecomment-361480731^0|1O|2|0|0|0|0|E|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|D|@$9|12|A|13|1|14]]|E|$]]|$1|O|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

This happens because the configuration for GitHub Desktop on Windows assumes CRLF but the text editor may be using LF. You can change your local repository settings to use <code>lf</code> instead.
Navigate to the root of the git repo and execute this in exact same order
<pre><code>git config core.eol lf
git config core.autocrlf input
</code></pre>
<a href="https://github.com/desktop/desktop/issues/3841#issuecomment-361480731" rel="noreferrer">Source: GitHub issue</a>

blocks|key|1188719|text|关闭Visual+|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1188720|如果您得到错误，一个简单的修复关闭Visual，您可以提交到main，这是很容易的。我也有同样的问题，我就是这样解决的。这是因为要打开的文件是在另一个程序中打开的。|1188721|entityMap^0|0|9|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Close Visual Studio
If you get the error, a simple fix is closing Visual Studio and you can commit to main, it is that easy.
I had this same problem and that was how I fixed it. It is caused because the files you want to open are open in another programm.

env:

<ul>
<li>Windows 7 </li>
<li>msysgit </li>
</ul>

Wheng I <code>git commit</code>, it says: 

<pre><code>warning: LF will be replaced by CRLF. 
</code></pre>

Is this warning tail backward? 
I edit file in Windows, the end of line is <code>CRLF</code>, just like this pic: 
<img src="https://i.stack.imgur.com/IMh60.jpg" alt="enter image description here"> 
And git changes it to <code>LF</code> for committing to repo. 
So I think the correct warning is: 

<pre><code>warning: CRLF will be replaced by LF. 
</code></pre>

Windows git "warning: LF will be replaced by CRLF", is that warning tail backward?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

环境规划署：Windows 7麦斯吉特git commit，上面写着：warning: LF will be replaced by CRLF. 这是警告尾向后吗？我在Windows中编辑文件，行的末尾是CRLF，就像下面的图片：git将其更改为LF，以便提交回购。因此，我认为正确的警告是：warning: CRLF ...

问Windows git“警告: LF将被CRLF取代”，这是警告尾向后吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Windows git“警告: LF将被CRLF取代”，这是警告尾向后吗？EN