From: Marc Strapetz Date: Fri, 13 Nov 2009 11:01:01 GMT Subject: Re: git status internals and line endings Message-ID: <4AFD3C6D.3010008@syntevo.com> In-Reply-To: <40aa078e0911130104v6acdecedxf629c5ef35a62740@mail.gmail.com> > In order to make changes to core.autocrlf effective, you need to > delete .git/index and perform a hard reset: > $ rm .git/index > $ git reset --hard This solved my problem. Thank you! -- Best regards, Marc Strapetz ============= syntevo GmbH http://www.syntevo.com http://blog.syntevo.com Erik Faye-Lund wrote: > On Fri, Nov 13, 2009 at 9:08 AM, Marc Strapetz > wrote: >>> Sounds like the core.autocrlf setting (see "git help config"), which I >>> believe is set by default on Windows. >> I have checked both $GIT_DIR/config and ~/.gitconfig and autocrlf has >> not been set. I have then set autocrlf = false for the Windows >> repository and still the file didn't show up as modified. On Linux, I've >> added autocrlf = true (resp. autocrlf = input) for the repository and >> still the file shows up as modified. Not that I don't like this >> behavior, but I don't understand it :) Windows Git version is 1.6.5.1, >> Linux version is 1.6.3.3. >> > > In order to make changes to core.autocrlf effective, you need to > delete .git/index and perform a hard reset: > $ rm .git/index > $ git reset --hard > > Did you do this before checking if the files were modified? >