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
warning: LF will be replaced by CRLF in index.html.
The file will have its original line endings in your working directory.
warning: LF will be replaced by CRLF in index.html.
The file will have its original line endings in your working directory.
warning: LF will be replaced by CRLF in manifest.appcache.
The file will have its original line endings in your working directory.
warning: LF will be replaced by CRLF in manifest.webapp.
The file will have its original line endings in your working directory.
This is using the full installer for Git 1.7.10-preview20120409.exe.
This doesn't actually cause any harm, but looks annoying and is likely to be confusing. It's almost certainly related to one of the options presented in the git installer (I left them all set to default).
@jrburke presumably create-responsive-template will have the same issue.
The text was updated successfully, but these errors were encountered:
Lots of warnings doing ghdeploy on windows:
warning: LF will be replaced by CRLF in index.html.
The file will have its original line endings in your working directory.
warning: LF will be replaced by CRLF in index.html.
The file will have its original line endings in your working directory.
warning: LF will be replaced by CRLF in manifest.appcache.
The file will have its original line endings in your working directory.
warning: LF will be replaced by CRLF in manifest.webapp.
The file will have its original line endings in your working directory.
This is using the full installer for Git 1.7.10-preview20120409.exe.
This doesn't actually cause any harm, but looks annoying and is likely to be confusing. It's almost certainly related to one of the options presented in the git installer (I left them all set to default).
@jrburke presumably create-responsive-template will have the same issue.
The text was updated successfully, but these errors were encountered: