What does "!eol" in gitattributes do?

Git has 2 attributes that deal with end-of-lines:

1. text

Documentation says:

This attribute enables and controls end-of-line normalization. When a text file is normalized, its line endings are converted to LF in the repository

This effectively means that when you commit to the repo, it will convert line-endings to LF

2. eol

Documentation says:

This attribute sets a specific line-ending style to be used in the working directory. It enables end-of-line normalization without any content checks, effectively setting the text attribute.

So while the text attribute affects how the file will look like IN THE REPO, eol affects how the file looks like in the working directory.

Now, an attribute can have 4 states:

set with no value
example: * text

unset
example: * -text

set with specific value
example: * text=auto

unspecified
example: * !text

So, * text=auto !eol means this:

All files have the attribute text set to auto and the eol attribute unspecified. Reading the documentation we find out that text=auto means that you let git decide if a file is text and if it is it will normalize it (set line-endings in the repo to LF).

!eol means that the attribute eol is set to unspecified explicitly. In this case it is the same as not specifying it at all, instructing Git to look at the core.eol config setting to see how to deal with line-endings in the working directory. Note this:

The core.eol configuration variable controls which line endings Git will use for normalized files in your working directory; the default is to use the native line ending for your platform, or CRLF if core.autocrlf is set.

But you would use !eol in a situation like the following:

* text=auto eol=CRLFtest.txt !eol

basically overriding the eol attribute from CRLF to unspecified for test.txt. This means that for all files except test.txt, Git will convert on checkout EOLs to CRLF but will do nothing to test.txt.

* text=auto !eol

implies:

• no EOL (end of line) conversion would be performed for binary files.
• for text files, EOLs are converted to OS-dependent EOL (convert to LF for Unix and CR+LF for Windows) upon checking out the file and replaced with LF while checking in.

It basically disables eol according to the documentation:

Sometimes you would need to override an setting of an attribute for a path to Unspecified state. This can be done by listing the name of the attribute prefixed with an exclamation point !.

eol does the following:

This attribute sets a specific line-ending style to be used in the working directory. It enables end-of-line normalization without any content checks, effectively setting the text attribute.