Skip to main content

Timeline for Make 'git diff' ignore ^M

Current License: CC BY-SA 4.0

13 events
when toggle format what by license comment
Mar 1, 2022 at 12:52 history edited gitaarik CC BY-SA 4.0
added 1 character in body
Mar 20, 2021 at 10:41 history edited gitaarik CC BY-SA 4.0
added 55 characters in body
Mar 19, 2021 at 0:14 comment added Orace You state that Windows use CR but actually it use CRLF. Files with CR only at e.o.l. are from mac os 9 and prior. en.wikipedia.org/wiki/Newline
Nov 19, 2020 at 23:35 comment added infoclogged should'nt it be *.ext text eol=lf inplace of of crlf ? I think that was a typo, that noone noticed !
Jan 29, 2020 at 17:35 comment added RJFalconer -1 as reinstalling git to accomplish git config --global core.autocrlf true is overkill, and the anti-Windows/anti-CR campaign seems tangential to the question.
Jan 29, 2020 at 17:32 history edited RJFalconer CC BY-SA 4.0
Fix bad grammar
Dec 20, 2016 at 16:36 history edited gitaarik CC BY-SA 3.0
added 11 characters in body
Dec 20, 2016 at 16:07 history edited gitaarik CC BY-SA 3.0
added 112 characters in body
Jun 23, 2016 at 12:11 comment added gitaarik Good one, I think it's just a "different" newline (different than most others)
Jun 22, 2016 at 19:01 comment added buhtz What exactly does this ^M means? Is it a windows or linux newline? Or is it just a "different" newline compared to the other newlines in the file?
Mar 27, 2015 at 16:37 history edited gitaarik CC BY-SA 3.0
added 31 characters in body
Mar 27, 2015 at 15:58 comment added Topher Hunt To fix all line endings in a specific file, if using Sublime Text, you can go to View -> Line Endings and click on Unix.
Oct 21, 2014 at 15:55 history answered gitaarik CC BY-SA 3.0