Re: core.autocrlf considered half-assed
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 8, 2010, 20:31 UTC
- Message-ID
- <7v6356r1w9.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <alpine.DEB.1.00.1003082011440.14277@intel-tinevez-2-302>
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. I know you wanted to have a sample repository that people can easily access and understand what you see as a problem, and the autogenerated 'html' is a good sample to point at for that purpose, but "even long-time gitsters..." is stretching the truth.
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.