Hi, On Thu, 24 Jul 2008, Steffen Prohaska wrote: > Dscho, > Is the following your use case? > > "I am the maintainer of this project. I know that this project needs > crlf conversion, because it is a cross-platform project. Therefore, > I want to force crlf conversion for this specific project, even if > the user did not configure core.autocrlf=input on Unix." No. My use case is this: a few users work on Windows (Cygwin), others on MacOSX, yet others on Linux. We often integrate files from somewhere else, and them Windows guys love to edit their files with their anachronistic proprietary crap tools that add CRs where CRs no belongee. Also, the Windows guys (being Windows guys) cannot be bothered to read documentation, so they did not set autocrlf. > Your patch provides a solution, though not a very comfortable one. With > your patch applied, you could explicitly list all files (or filetypes) > that are text and mark them with 'crlf'. Why should I want to do that? I do not _want_ CRs. And them Windows guys do not need them either; they are often not even aware that their crap tools introduce them. > You could also specify 'crlf=input', but I don't understand why you want > to specify this. That's what I do. And _I_ need to understand why ;-) Well, seems I will just continue shouting "why did you commit that CR-ridden file?" and get shouted back with "why does this §&%&%&!° Git tool not fix it for me automatically? Even _Subversion_ can do it." Ciao, Dscho
