When working in a multi-OS team, there needs to be a common standard for the text file line endings.
Given that Git was designed as the version control system for Linux, the Unix LF line ending was chosen as the default setting for storage _within_ the repository. This means that users on Windows should (it's a choice;-) get Git to convert any CRLF line endings in text files to the standard LF ending when stored into the repository, and convert them back to CRLF when extracting from the respository for local use. There are some more discussions in the git attributes and config man pages regarding how text files and binary files are determined for the end of lince conversion. Philip On Saturday, October 10, 2020 at 1:43:20 PM UTC+1 [email protected] wrote: > Why we need to setup the > git config --global autocrlf true > in windows and > git config --global autocrlf input > in macOS/linux. > > What's the significance of these two different commands ? and Why are they > important -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/d1f72932-bb25-4c2e-836b-41b2e61d88can%40googlegroups.com.
