我正在从存储库中 check out ，我是 Mac 和 Linux 海洋中唯一的 Windows 用户。我的 IDE 在我的 Windows 机器上运行，代码被推送到 VM。代码不会同步回主机。当我准备好在我的 Windows 主机上添加/提交时，我收到了 warning: LF will be replaced by CRLF 消息。

这些是我的 Git 设置:

core.symlinks=false
core.autocrlf=true
core.fscache=true
color.diff=auto
color.status=auto
color.branch=auto
color.interactive=true
help.format=html
http.sslcainfo=C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt
diff.astextplain.textconv=astextplain
rebase.autosquash=true
credential.helper=manager
core.editor='C:/Program Files/Notepad++/notepad++.exe' -multiInst -nosession
core.filemode=false
core.repositoryformatversion=0
core.filemode=false
core.bare=false
core.logallrefupdates=true
core.symlinks=false
core.ignorecase=true

我不确定为什么 core.filemode=false 被列出了两次。

为什么我会在 Windows 上收到此警告？我是否在我的设置中做了一些愚蠢的事情(完全可能)？或者，这在这种情况下是否有意义，如果是，为什么？

最佳答案

Git 有两个地方可以控制换行:

• 在您系统的全局配置设置中
• 在每个 repo /项目适用的 .gitattributes 文件中。这些设置将覆盖用户的配置设置。

在您的 Git 设置中，您有 core.autocrlf=true。这意味着您要告诉 Git 将行结尾更改为 CRLF。您可以更改它以查看 Git 是否停止尝试更改行尾。

git config --global core.autocrlf input

更好的方法可能是在 .gitattributes 文件中设置正确的行结尾。这将提交到根目录中的存储库，它将覆盖用户的个人设置。这确保所有提交 repo 协议(protocol)的用户都有正确的行尾。因为听起来您正在处理基于 *nix 的项目，所以将行尾设置为换行可能是明智的。在 .gitattribute 文件中你可以有这样的东西。

# Set all files to have LF line endings
* text eol=lf

此链接对您可以在文件中设置的选项有更详细的解释:https://help.github.com/articles/dealing-with-line-endings/

编辑 1:以为我是从实际的 Git 文档中添加的:https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration

core.autocrlf

If you’re programming on Windows and working with people who are not (or vice-versa), you’ll probably run into line-ending issues at some point. This is because Windows uses both a carriage-return character and a linefeed character for newlines in its files, whereas Mac and Linux systems use only the linefeed character. This is a subtle but incredibly annoying fact of cross-platform work; many editors on Windows silently replace existing LF-style line endings with CRLF, or insert both line-ending characters when the user hits the enter key.

Git can handle this by auto-converting CRLF line endings into LF when you add a file to the index, and vice versa when it checks out code onto your filesystem. You can turn on this functionality with the core.autocrlf setting. If you’re on a Windows machine, set it to true – this converts LF endings into CRLF when you check out code:

$ git config --global core.autocrlf true

If you’re on a Linux or Mac system that uses LF line endings, then you don’t want Git to automatically convert them when you check out files; however, if a file with CRLF endings accidentally gets introduced, then you may want Git to fix it. You can tell Git to convert CRLF to LF on commit but not the other way around by setting core.autocrlf to input:

$ git config --global core.autocrlf input

This setup should leave you with CRLF endings in Windows checkouts, but LF endings on Mac and Linux systems and in the repository.

If you’re a Windows programmer doing a Windows-only project, then you can turn off this functionality, recording the carriage returns in the repository by setting the config value to false:

$ git config --global core.autocrlf false

关于windows - 在 Windows 上工作，但在 Git 中提交时得到 "LF will be replaced by CRLF"，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/43023096/