Re: CRLF problems with Git on Win32

From: Johannes Schindelin <johannes.schindelin-mmb7mzphnfy@public.gmane.org>
Date: Jan 9, 2008, 11:03 UTC
Message-ID: <alpine.LSU.1.00.0801091100401.31053@racer.site>
In-Reply-To: <B655B6FF-9377-434A-A979-2E758771B0FA-wjoc1KHpMeg@public.gmane.org>

Hi,

On Tue, 8 Jan 2008, Steffen Prohaska wrote:

Show 13 quoted lines

> On Jan 8, 2008, at 8:47 PM, Junio C Hamano wrote:
> 
> > I think the project can mark text files as text with attributes and if 
> > the port to the platform initialized core.autocrlf appropriately for 
> > the platform everything should work as you described.
> > 
> > At least that is how I read the description of `crlf` in 
> > gitattributes(5).
> 
> But we do not want to mark a file as text but tell git to run its 
> auto-detection and use the local default line endings.  But for 
> different projects we do not even want to run the auto-detection, but 
> leave the files as is.

Probably the best thing would be to default to crlf=true, and then have a .gitattributes file like this in your project:

-- snip -- *.am -crlf -- snap --

(Did I guess right about the file extension? But why do you want to check in huge 3D stacks? Ah, of course, for test cases.)

Ciao, Dscho