To check what line endings were actually committed in the repository (regardless of your core.autocrlf setting), try the following: git grep -I –files-with-matches –perl-regexp ‘\r’ HEAD (-I means that binary files should not be looked at.)
I’m interested in this too. Supposing you have a repo that was created via git svn clone, I think you could break it down into three different questions: Does any git newline normalization/alteration happen at git svn fetch time, in moving commits from svn to the git repo? Does any git newline normalization/alteration happen at … Read more
very new to this so setting core.autocrlf to false didn’t make too much sense to me. So for other newbies, go to the config file in you .git folder and add: [core] autocrlf = false under the [core] heading.
This seems like a bug in msysgit indeed. As a workaround, try creating a .gitattributes file containing * -text This will tell git not to perform EOL conversions on any files.
git config –global core.autocrlf false Has always been my recommendation (see “Git 1.6.4 beta on Windows (msysgit) – Unix or DOS line termination”). However, in your case, you can “Continue”, but this warning is there to mention the conversion of certain files might not be reversible: core.safecrlf If true, makes git check if converting CRLF … Read more
The best way to avoid having to set core.autocrlf separately on each machine seems to be checking a .gitattributes file into the repository containing the single line * -text Or, if you have an older version of Git then * -crlf This tells Git that, for all paths (thus the *), end-of-line normalization should not … Read more
The three values for autocrlf: true – when content goes into the repository (is committed), its line endings will be converted to LF, and when content comes out of the repository (is checked out), the line endings be converted to CRLF. This is in general meant for clueless windows users/editors. Given the assumption that an … Read more
Ah ah! Checkout the previous commit, then checkout the master. git checkout HEAD^ git checkout -f master
The error message suggests that the script you’re invoking has embedded \r characters, which in turn suggests that it has Windows-style \r\n line endings instead of the \n-only line endings bash expects. As a quick fix, you can remove the \r chars. as follows: sed $’s/\r$//’ ./install.sh > ./install.Unix.sh Note: The $’…’ string is an … Read more
The best explanation of how core.autocrlf works is found on the gitattributes man page, in the text attribute section. This is how core.autocrlf appears to work currently (or at least since v1.7.2 from what I am aware): core.autocrlf = true Text files checked-out from the repository that have only LF characters are normalized to CRLF … Read more