For example, Git automatically determines whether files in a repository are text or binary files. To ensure that all the line endings in your repository match your new configuration, back up your files with Git, then remove and restore all of the files to normalize the line endings.īefore adding or committing any changes, verify that Git has applied the configuration correctly. You may find that Git reports changes to files that you have not modified. gitattributes file, Git automatically changes line endings to match your new configuration. Refreshing a repository after changing line endingsĪfter you set the tocrlf option or commit a. The binary setting is also an alias for -text -diff. You should use this for files that must keep LF endings, even on Windows.īinary Git will understand that the files specified are not text, and it should not try to change them. Text eol=lf Git will always convert line endings to LF on checkout. You should use this for files that must keep CRLF endings, even on OSX or Linux. Text eol=crlf Git will always convert line endings to CRLF on checkout. Text=auto Git will handle the files in whatever way it thinks is best. We'll go over some possible settings below. You'll notice that files are matched- *.c, *.sln, *.png-, separated by a space, then given a setting- text, text eol=crlf, binary. # Denote all files that are truly binary and should not be modified. # Declare files that will always have CRLF line endings on checkout. # Explicitly declare text files you want to always be normalized and converted You can use it as a template for your repositories: # Set the default behavior, in case people don't have tocrlf set.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |