Re: Problems with autoCRLF?

From: Junio C Hamano <junkio@cox.net>
Date: Mar 10, 2007, 01:24 UTC
Message-ID: <7v8xe528mk.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <1173464102.6102.18.camel@localhost>

Raimund Bauer <ray007@gmx.net> writes:

> Is it really intended that with a setting core.autoCRLF=true textfiles
> are checked out with crlf-lineendings on linux-boxes?

Yes. The implicit assumption with any setting to core.autoCRLF is that you want to keep the git objects free of CRLF line endings.

 - core.autoCRLF 'true' means that your tools that handle text
   files would be upset findign LF line endings, and they will
   leave text in CRLF line endings.  Checking out from git
   creates working tree files while adding CR before LF as
   needed, and checking in from working tree files to git strips
   CR before LF as needed.

 - core.autoCRLF 'input' means that your tools do not mind
   handling text files in LF line endings and they will leave
   text in CRLF line endings, so checking out from git creates
   working tree files by just giving what is stored in the
   repository, and checking in from working tree files to git
   strips CR before LF as needed.

So on sane platforms, you do not want to set that variable, unless you are helping to test and improve that feature.