On 24.01.22 10:53, Konstantin Khomoutov wrote:
Yes: setting both core.autocrlf to "false" and core.eol to "crlf" should defeat Git's EOL normalizations.
The problem is that I don't want to defeat it. I want to apply it in the other direction.
My problem is: the project I'm working on originated on DOS, all text files have been checked in with DOS line endings, and that isn't going to change (i.e. a monster commit that replaces every CRLF with LF, project-wide, isn't in the cards). However, I want to process the files with standard Linux programs and standard editor settings, without seeing a heap of spurioous ^M characters at the end of every second line. I also don't want to accidentally add a file with LF endings to the index. (Yes that can be prevented with hooks, but that's a partial and sub-optimal solution.)
-- -- Matthias Urlichs -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/2223af74-3696-7d9b-0275-8652cee74fb0%40urlichs.de.
<<attachment: matthias.vcf>>
OpenPGP_signature
Description: OpenPGP digital signature
