Still for #791. I've run: git add --renormalize .
#794
Conversation
I've run: `git add --renormalize .` Reason: On some, but not all files, when I try to make changes , Github recognises the whole file as modified. In the Internet it is recommended to run `git add --renormalize .` and to create a pull request for the result, after the handling of line endings has changed. This is what I've done. There are no actual changes in the files. You can check with Beyond Compare.
|
@stephanstapel Just a bit more background information about why this pull request is required. What I want to achieve is, that on the server the files are stored with Unix line endings, but when checked out on a Windows system they are converted to Windows line endings. This is what Git does when "core.autocrlf" is set to "true" (although I'm using "core.autocrlf" set to "false"). The "problem" is that some developers, who have worked on ZUGFeRD-csharp, don't have "core.autocrlf" set to "true", but to "false" (like me). This means that currently there's on the server a mixture of different line endings. Some files have Unix style line endings, some have Windows style line endings and some even a mixture. With When you view the files with e.g. Beyond Compare, you will see that "AssociatedDocument_raw.cs" has Unix style line endings, but "BankAccount_raw.cs" has Windows style line endings: This commit cleans this up, so that on the server all files consistently will have Unix style line endings. |
Still for #791.
I've run:
git add --renormalize .Reason: On some, but not all files, when I try to make changes , Github recognises the whole file as modified.
In the Internet it is recommended to run
git add --renormalize .and to create a pull request for the result, after the handling of line endings has changed.This is what I've done.
There are no actual changes in the files. You can check with Beyond Compare.