> On 9. mai 2010, at 13.14, Robert Buck wrote:
quoted text
>
>> So, the meanings of these would become...
>>
>> core.crlf [ auto | input | false ] : 'auto' means to enable
>> bidirectional normalization, and 'false' would mean do not
>> normalization, and 'input' would mean normalize on input only,
>> otherwise output lf. Is this true?
>
> No, "auto" means to enable normalization for files git doesn't identify as text files, "true" means to always normalize, and "false" means never normalize.

I probably missed something. The part that confuses me in this
statement is that you said "for files git doesn't identify as text
files". The convert.c source is the heart of this, and if a file is
not identified as text it is presumed to be binary. The statement made
seems to imply you'd auto-convert PDF files? I know you did not mean
that, but it could have been read that way.

What specifically happens in the three modes? Would it be precise to
say the following?

    "Files subject to EOL conversion are those that are explicitly
identified through attributes to be text files, or those
algorithmically determined to be text files which happen to not bear
the "text" file attribute. Otherwise the default value, "false",
applies and no EOL conversions occur."

-Bob
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html