Closed wimleers closed 12 years ago
Thank you for this excellent suggestion :-) I added the .gitattributes file and converted existing CRLF -> LF. The .gitconfig would be interesting too, but I can't seem to get it to work....
You may need to perform the steps listed under "Re-normalizing a repo" on GitHub's recommendations page I linked to earlier.
Does that help?
Oh, also, you can reference GitHub issues in commit messages by prepending #
to the issue number or pull request number.
So e.g. Convert CRLF to LF. Fixes #610.
would've automatically closed this issue :)
See https://github.com/blog/831-issues-2-0-the-next-generation, "Commits + Issues" heading.
I did perform the re-normalizing step for line endings.
The whitespace = space-before-tab... setting doesn't work like that it seems. I think what we need is some tool that fixes existing whitespace problems.
Also, thank you for the info, I will reference commits in the future.
Maybe it's a git version issue?
$ git --version
git version 1.7.10.2
I think this issue should be closed; I'd say #739 is the successor.
Many big open source projects, including Drupal, specify very precise expectations about the code: coding standards. They even specify expectations about whitespace:
Conforming to these coding standards prevents collaboration issues.
With the following
~/.gitattributes
file (which is recommended by GitHub):I get the following automatic changes performed by
git
:Would you be willing to to solve this problem? It's definitely a problem other contributors will run in to at some point.
P.S.: the following
~/.gitconfig
additions ensure even cleaner code: