Re: core.autocrlf & Cygwin - files incorrectly flagged as modified

From: David Antliff <david.antliff@gmail.com>
Date: Dec 18, 2009, 02:43 UTC
Message-ID: <loom.20091218T033941-445@post.gmane.org>
In-Reply-To: <200912170800.35752.robin.rosenberg@dewire.com>

Robin Rosenberg writes:

Show 9 quoted lines

> tisdag 15 december 2009 23:24:15 skrev  David Antliff:
> > The problem is that sometimes, after a git-clone, the output of git-status
> >  and git-diff shows entire files as being different. However these files
> >  have not been modified by the user - only git has had a chance to change
> >  them (due to autocrlf=true). But surely if git has converted the file
> >  automatically, it should know that it has to compensate for this when
> >  comparing with the local repository?
> 
> AFAIK, this happens if you have CRLF line endings in the blobs in the repo.

Oh? That could very well be true - how would such line endings get into a blob? I'm pretty sure everyone is using autocrlf=true which should convert all line endings to LF on commit, but perhaps there's another way to get CRLF line endings into a blob?

If autocrlf=false, files are committed as-is (I believe), so this would be one way to end up committing such files. But as far as I know, nobody has turned that option off in our group.