Confusing note in "gitattributes text=auto" discription

Confusing note in "gitattributes text=auto" discription

[Hebrock, Christoph]

Dear Sir or Madam,
I have a question about "gitattributes text".

I find the sentence "When the file has been committed with CRLF, no conversion is done" somewhat confusing in the context descibed above.
How is this possible when "text=auto" is active to commit/checkin CRLF?

Set to string value "auto"
When text is set to "auto", the path is marked for automatic end-of-line conversion. If Git decides that the content is text, its line endings are converted to LF on checkin. 
"When the file has been committed with CRLF, no conversion is done."


With kind regards
Christoph Hebrock

Re: Confusing note in "gitattributes text=auto" discription

[Torsten Bögershausen]

On Mon, May 09, 2022 at 10:59:08AM +0000, Hebrock, Christoph wrote:
> Dear Sir or Madam,
> I have a question about "gitattributes text".
>
> I find the sentence "When the file has been committed with CRLF, no conversion is done" somewhat confusing in the context descibed above.
> How is this possible when "text=auto" is active to commit/checkin CRLF?
>
> Set to string value "auto"
> When text is set to "auto", the path is marked for automatic end-of-line conversion. If Git decides that the content is text, its line endings are converted to LF on checkin.
> "When the file has been committed with CRLF, no conversion is done."

This is what happens in real live, and what we try to describe:
#On a Windows box:
mkdir test_repo
cd test_repo
git init
git config core.autocrlf false
printf 'REM my first BAT file\r\n' >test.bat
printf 'REM exit' >>test.bat
git add test.bat
git commit -m "Add test.bat"

git ls-files --eol
# Something in this style:
i/crlf w/crlf attr/            test.bat

Now the file has been commited with CRLF.

Does this answer the question ?