You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Why add directive to "repository" create, so that an initial commit is created with expected ".gitattributes" content, which would allow LFS support too?
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: