Conversation
|
Not a big fan to be honest, because it updates
Besides the aesthetics, is there a functional reason for this? |
|
I concur with @kba. Adding:
IMO we don't need these cosmetics, least now. |
|
These objections are not new, and some of them are easy to solve (for example by ignoring whitespace changes). But there is a common consensus among most open source projects that these kinds of whitespace should not be part of the code base. That's the reason why Git marks commits with such whitespace issues and why Ideally the code base should be cleaned, also in upstream projects. That makes it easier to maintain the code because editors then can avoid further whitespace issues without changing existing lines with such issues. It also reduces the size of an installation by a few bytes. A minimal requirement should be a check for new contributions which marks those with issues as invalid. The Linux kernel provides a very powerful script which does that, but might not be usable because of the license conflict. |
|
I rebased and updated this pull request. The bad news is that now 29 files show whitespace issues. Some months ago 26 files were affected. |
Signed-off-by: Stefan Weil <sw@weilnetz.de>
Signed-off-by: Stefan Weil <sw@weilnetz.de>
Signed-off-by: Stefan Weil <sw@weilnetz.de>
Use
git log --checkto see the commits which introduced trailing whitespace.