We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What steps will reproduce the problem? Steps to reproduce the behavior:
What is the expected output? Commited, nothing more
What happens instead? git status show that the file is restaged (this time apparently due to changed line endings):
modified: src/x/y.java
I can see the original file has CRLF line endings, the temporary file has LF line endings and the restaged file has CRLF endings again.
When I recommit again the staged file (that is not to be reformatted then), the commit is successful without being restaged.
Environment:
Link to a git repository that can be cloned to reproduce the problem:
Additional context No problems when autocrlf=false
The text was updated successfully, but these errors were encountered:
Probably a duplicate of #96 - sorry :(
Sorry, something went wrong.
No branches or pull requests
What steps will reproduce the problem?
Steps to reproduce the behavior:
What is the expected output?
Commited, nothing more
What happens instead?
git status show that the file is restaged (this time apparently due to changed line endings):
modified: src/x/y.java
I can see the original file has CRLF line endings, the temporary file has LF line endings and the restaged file has CRLF endings again.
When I recommit again the staged file (that is not to be reformatted then), the commit is successful without being restaged.
Environment:
Link to a git repository that can be cloned to reproduce the problem:
Additional context
No problems when autocrlf=false
The text was updated successfully, but these errors were encountered: