Re: CRLF problems with Git on Win32

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Jan 11, 2008, 18:10 UTC
Message-ID: <alpine.LFD.1.00.0801111005360.3148@woody.linux-foundation.org>
In-Reply-To: <930EC77A-73D1-4DDD-81D4-BF22B248FCB6@zib.de>

On Fri, 11 Jan 2008, Steffen Prohaska wrote:

Show 9 quoted lines

> 
> Ah sorry, I misunderstood you in [1].  I thought your last point
> "Mixed Windows usage" meant what I have in mind:  A user working
> in a mixed Windows/Unix environment who creates a file using
> Windows tools and commits it in the Unix environment.  In this
> case the CRLF file will be transferred from Windows to Unix
> without git being involved.  The right thing for git on Unix is
> to remove CRLF during a commit but still write only LF during
> check out.  So autocrlf=input is the right choice.

Oh, ok, I didn't realize.

But yes, if you use a network share across windows and Unixand actually *share* the working tree over it, then yes, you'd want "autocrlf=input" on the unix side.

However, I think that falls under the "0.1%" case, not the "99.9%" case.

I realize that people probably do that more often with centralized systems, but with a distributed thing, it probably makes a *ton* more sense to have separate trees. But I could kind of see having a shared development directory and accessing it from different types of machines too.

I'd also bet that crlf behavior of git itself will be the *least* of your problems in that situation. You'd have all the *other* tools to worry about, and would probably be very aware indeed of any CRLF issues. So at that point, the "automatic" or default behaviour is probably not a big deal, because everything _else_ you do likely needs special effort too!

			Linus