-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Unstaged changes #1228
Comments
Very strange, although I can’t reproduce it on Mavericks on my Macbook Air, tried git v1.7.12.1 and v1.8.4.3 (Homebrew hasn’t got v1.9.0 yet), both HTTPS and SSH. Don’t know what to suggest… |
I get the same issue as @alrra. To fix this, please run the following commands:
and commit all changes (which should be exactly this one file as seen in @alrra's comment). You might want to add a .gitattributes files to the repository in order to prevent issues like this beforehand. Please see this help page. |
@stucox thanks for testing (btw, I had this issue, even before I've updated to
@stucox It has (see: Homebrew/legacy-homebrew#26734). |
Fix line ending issue described in #1228
Setting text=auto will ensure line endings to be normalized to LF. This prevents changed files on different systems after cloning the project. Reference Modernizr#1228. Closes Modernizr#1231.
This commit resolves the issue described in Modernizr#1228, and thus, eliminates the problem where users on platforms with a different native line ending, get unstaged changes. Close Modernizr#1228.
Fix line ending issue described in Modernizr#1228
This is kinda weird, but after cloning Modernizr, I get some unstaged changes:
I'm using
git v1.9.0
on Mac OS X.The text was updated successfully, but these errors were encountered: