Add .gitattributes with auto line feed treatment #902
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
* text=auto
option causes the line endings in text files to be normalized to LF on check-in, but reset to the platform-specific version on check-out.This should ensure consistency of the repo throughout development on different platforms, while providing platform-specific line endings in the working directory. After some double-checking this seems to be the safest option to ensure global consistency for multi-platform development.
In its current version
.gitattributes
lets git decide what is/isn't a text file. This is not an issue in the for cppfront as all files in the repo are text. However, if it becomes necessary, further configuration can be added to the file to ensure certain files/files with certain extensions are treated as binary and so untouched on check-in/check-out.In addition, to avoid the pain of diffs with only line ending differences in regression tests I have been using: