Re: core.autocrlf considered half-assed

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mar 8, 2010, 11:29 UTC
Message-ID: <alpine.DEB.1.00.1003081225280.14277@intel-tinevez-2-302>
In-Reply-To: <20100307092701.GC31105@dpotapov.dyndns.org>

Hi,

On Sun, 7 Mar 2010, Dmitry Potapov wrote:

Show 12 quoted lines

> On Sat, Mar 06, 2010 at 12:23:33AM +0100, Johannes Schindelin wrote:
> 
> > Just try to "git reset --hard" or "git stash" when there are files 
> > with DOS line endings and when core.autocrlf is not false.
> 
> I did, and I have not noticed any problem with that.
> 
> git init
> git config core.autocrlf true
> echo foo^ | tr ^ '\r' > foo
> git add foo
> git commit -m 'add foo'

Unfortunately, this is not the common case. The common case is that somebody committed _without_ autocrlf (implicitly =false), and you clone from there.

Easiest example:

$ git clone -n git://repo.or.cz/git.git html-docs $ cd html-docs/ $ git config core.autocrlf true $ git checkout -t origin/html $ git status

... and despair.

Hth, Dscho