Re: mingw, windows, crlf/lf, and git

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 13, 2007, 18:04 UTC
Message-ID: <Pine.LNX.4.63.0702131901040.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <Pine.LNX.4.64.0702130845330.8424@woody.linux-foundation.org>

Hi,

On Tue, 13 Feb 2007, Linus Torvalds wrote:

Show 18 quoted lines

> On Tue, 13 Feb 2007, Johannes Schindelin wrote:
> > 
> > On Tue, 13 Feb 2007, Alexander Litvinov wrote:
> > 
> > > The only trouble is the rebase, it does not like \r\n ending and 
> > > othen produce unexpected merge conflict. But I don't use rebse to 
> > > othen to realy investigate and try to solve the problem.
> > 
> > Well, if everybody thinks like you, maybe we do not have to change 
> > anything for Windows after all?
> 
> No no no.
> 
> It's going to be _horrible_ if people start interesting projects in 
> Windows, and there are files in a git repository that are encoded with 
> CRLF.
> 
> I'd much rather just get this right, and that means "no hooks".

No hooks means something like cvsnt does, and that means no .gitattributes either. (BTW I really hate .gitattributes, as it does not at all say what this is about; it's about file _conversions_, not attributes).

CVSNT analyzes the files, and guesses if they are text, and only then activates the text mode.

I am strongly opposed to including something like that. (It was already proposed, and your "no hooks" suggests the same.)

However, I am slightly positive about the .gitfiletypes approach, _iff_ we think about more than just text/binary from the start. If we do it right, it will buy us more.

Ciao, Dscho