-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to handle end-of-lines normalization #67
Labels
Comments
Why add directive to "repository" create, so that an initial commit is created with expected ".gitattributes" content, which would allow LFS support too? |
Good question. At this point, my workaround is to try lint-history: lint-history dos2unix It's pretty fast on a huge repo anyway. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are facing issues after migration when users add
.gitattributes
file to keep LF for shell scripts when working on Windows platform."Perfect world" expectation would be that svn-all-fast-export inspected svn:eol-style Subversion property and applies ".gitattributes" for each imported commit.
What is the recommended way to get all text files with LF EOL in repository itself, so that Git attributes can be used seamlessly after migration when committing from different EOL-style platforms?
The text was updated successfully, but these errors were encountered: