From: Eyvind Bernhardsen <eyvind.bernhardsen@gmail.com>
Date: Mon, 24 May 2010 21:09:57 GMT
Subject: Re: What's cooking extra
Message-ID: <03D36B78-470F-47F8-8553-AF4A1464281F@gmail.com>
In-Reply-To: <20100524205612.GA28890@localhost>

On 24. mai 2010, at 22.56, Clemens Buchacher wrote:

> On Mon, May 24, 2010 at 04:47:34PM +0400, Dmitry Potapov wrote:
> 
>> On Mon, May 24, 2010 at 11:49:05AM +0200, Clemens Buchacher wrote:
>> 
>>> With CRLF file in the repository, core.autocrlf=true and
>>> core.eol=lf,
>> 
>> I wonder if this combination should be allowed. core.autocrlf=true
>> always implied that the native EOL is CRLF.
> 
> I just did what the commit message suggested:
> 
>    If core.eol is set explicitly (including setting it to "native"), it
>    will override core.autocrlf so that
> 
>    [core]
>            autocrlf = true
>            eol = lf
> 
>    normalizes all files that look like text, but does not put CRLFs in the
>    working directory.

Right.  While technically true, this is misleading in that it implies that you will get LF line endings on all your files.

I will update the documentation to reflect that core.autocrlf is only useful if you want to work with CRLF line endings in a repository that is not normalized.  I won't be able to do that for a week or so, unfortunately.
-- 
Eyvind