From: Jakub Narebski <jnareb@gmail.com>
Date: Mon, 10 May 2010 20:30:22 GMT
Subject: Re: [PATCH/RFC] autocrlf: Make it work also for un-normalized repositories
Message-ID: <m37hnbec16.fsf@localhost.localdomain>
In-Reply-To: <20100510171119.GA17875@pvv.org>

Finn Arne Gangstad <finnag@pvv.org> writes:

> Previously, autocrlf would only work well for normalized
> repositories. Any text files that contained CRLF in the repository
> would cause problems, and would be modified when handled with
> core.autocrlf set.
> 
> Change autocrlf to not do any conversions to files that in the
> repository already contain a CR. git with autocrlf set will never
> create such a file, or change a LF only file to contain CRs, so the
> (new) assumption is that if a file contains a CR, it is intentional,
> and autocrlf should not change that.
> 
> The following sequence should now always be a NOP even with autocrlf
> set (assuming a clean working directory):
> 
> git checkout <something>
> touch *
> git add -A .    (will add nothing)
> git comit       (nothing to commit)
> 
> Previously this would break for any text file containing a CR

How this feature relates to `core.safecrfl'?

-- 
Jakub Narebski
Poland
ShadeHawk on #git