From: Torsten Bögershausen <tboegi@web.de>
Date: Sat, 24 Jun 2017 22:02:43 GMT
Subject: Re: EOL LF Windows auto.crlf issue
Message-ID: <9825c435-d752-79b5-f474-964f1ded8c54@web.de>
In-Reply-To: <CADtLFZcQNziGJx-aW9pvUU-NTHcbRN8pHXecMtRgaYwqTjGZWQ@mail.gmail.com>



On 24/06/17 18:56, Filip Kucharczyk wrote:
> I'm on Windows 10.
> auto.crlf in .gitconfig is set to
> [core]
> autocrlf = true
> I've got a git (git version 2.13.1.windows.2) repo.
> A linux guy emails me a text with with line endings LF.
> I paste this file into my repo.
> Now every time I introduce changes to this file and stage it, git tell me:
> "warning: LF will be replaced by CRLF in a.txt.

This conversion will happen if you do
rm a.txt
git checkout a.txt

After these 2 steps, the file willhave CRLF in the working tree,
see below.
But if you don't, the file stays as it is in the working tree.

> The file will have its original line endings in your working directory."

> But when I commit the file git does not replace anyline endings - they
> stay LF in the commited file and in my working direcotry.

Yes, core.autocrlf=true tells Git that they should have CRLF in the working 
tree, at least after a clean checkout.
> I'm sort of misleaded by this message.
Suggestions how to improve things are of course welcome -
for your case it may help to set
git config core.autocrlf input
for this very repo.

> 
> Filip
>