I suggest disabling the core.autocrlf feature completely. It really screws up your commits if for some reason tools modify the line-endings. Nothing is more annoying than having a commit where you get a deletion/insert for every line in the document although you only changed 2 LOC.. In fact, I got so annoyed about this that I even blogged about that: http://www.tigraine.at/2010/02/03/disable-autcrlf-in-msysgit/
I still have no real explanation how inconsistent file endings started to occur on a Windows-only environment, but it happened a lot to me in the past, and I've seen too many commits being completely unreadable due to this. greetings Daniel On Sat, Feb 27, 2010 at 4:16 PM, Mauricio Scheffer < [email protected]> wrote: > If anyone's having problems with git diffs showing ^M or other weird > line-ending-related things, you need to set the core.autocrlf setting, > then refresh your working copy. Here are the instructions: > http://help.github.com/dealing-with-lineendings/ > > You can check if your files have CRLF (and not just LF) with a proper > text editor like Notepad++ > > Cheers, > Mauricio > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]<castle-project-devel%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
