Re: core.autocrlf considered half-assed

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mar 9, 2010, 09:28 UTC
Message-ID: <alpine.DEB.1.00.1003091026060.7596@pacific.mpi-cbg.de>
In-Reply-To: <7v6356r1w9.fsf@alter.siamese.dyndns.org>

Hi,

On Mon, 8 Mar 2010, Junio C Hamano wrote:

Show 12 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > And I demonstrated with the "html" example that even long-time 
> > Gitsters sometimes commit DOS line endings as-are, unconverted.
> 
> FWIW, not using CRLF conversion in the auto-generated 'html' repository
> was a deliberate choice, as the contents there (the ones generated by
> AsciiDoc with '.html' suffix) were intended to be served directly from the
> web servers.  I presume AsciiDoc writes them with CRLF because html
> documents are supposed to be, and it would be wrong to apply core.autocrlf
> in the auto-generated repository.  And it is not correct to force
> core.autocrlf on the recipient side either.

And here you are wrong, because the branch contains _also_ .txt files that are _not_ CR/LF, but need to be CR/LF on Windows. Believe me, we did think about what we were doing in msysGit. More than once.

> Nevertheless, I agree with you that if a similar situation happened by 
> mistake and your project does want to enforce core.autocrlf, it would be 
> nicer if there is an easy-to-use one-time clean-up procedure.  It hasn't 
> been my itch, and I suspect it wasn't Linus's itch either.

The problem is that the whole thing was not your itch, but your implementation. You never used it, so you never caught the obvious flaws in the design.

Sorry to be so direct, but it seems that my more subtle attempts to explain the situation failed.

Ciao, Dscho