Menu
We have this in our .gitattributes file:
* text=auto eol=lf I'd like to precisely understand what this does.
The first part is text=auto. From the documentation:
This ensures that all files that Git considers to be text will have normalized (LF) line endings in the repository.
The important part is that Git does the normalization only for files that it detects as text files.
However, I'm not sure about the eol=lf part. I would think that it will also do the normalization only for text files but I can't find support for it in the documentation and we had an instance when our PNG files were normalized too, making them invalid.
Is there a settings like the above that would basically say "do the normalization in both directions for text files, and leave binary files alone"?
513
gitattributes file allows you to specify the files and paths attributes that should be used by git when performing git actions, such as git commit , etc. In other words git automatically saves the file according to the attributes specified, every time a file is created or saved.
DESCRIPTION. A gitattributes file is a simple text file that gives attributes to pathnames. Each line in gitattributes file is of form: pattern attr1 attr2 ... That is, a pattern followed by an attributes list, separated by whitespaces.
These path-specific settings are called Git attributes and are set either in a . gitattributes file in one of your directories (normally the root of your project) or in the . git/info/attributes file if you don't want the attributes file committed with your project.
Git 2.10 fixed this and now behaves as one would expect.
131
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
