Re: crlf with git-svn driving me nuts...
- From
Avery Pennarun <apenwarr@gmail.com>
- Date
- Apr 16, 2008, 21:02 UTC
- Message-ID
- <32541b130804161402u736f4c02wa1c2b977d64e98ec@mail.gmail.com>
- In-Reply-To
- <46a038f90804161356o7518ec72j3bfb4e9fe4e48852@mail.gmail.com>
On 4/16/08, Martin Langhoff <martin.langhoff@gmail.com> wrote:
Show 9 quoted lines
> On Wed, Apr 16, 2008 at 3:01 PM, Dmitry Potapov <dpotapov@gmail.com> wrote: > > If you do not want problems, you should use core.autocrlf=true > > on Windows. > > If you are making the above statements in generally about git, I > disagree. I have used msysgit a lot with unix-newlines projects, and > it works fantastic. I am careful to work with newline-smart editors > but any half-decent editor will cope. The general hint is: avoid any > content-mangling options if possible, and git will do the right thing.
Various Windows IDEs (notably Delphi... and notepad :)) get confused by non-CRLF files and either do random things to the file, fail to compile, or "helpfully" change all the line endings back to CRLF. I agree that any program that does any such thing is braindead, but unfortunately, some people are stuck with such programs.
Avery