[Bf-committers] Pickly details (policy on triling whitespace)

Campbell Barton ideasman42 at gmail.com
Sat Dec 27 21:21:31 CET 2014


Regarding devs adding/removing trailing whitespace.

- https://developer.blender.org/rB0fc0cb351b5e838dce7a14e8fe68fb6f7125eab0
- https://developer.blender.org/rB5d8a207b67aee18cadec742246b9dc9c052bd344
- https://developer.blender.org/rBfd4720204399e16032574159699d5a26a250e6d5
- https://developer.blender.org/rB49052c61f8326c11bc733a040372481ea1d7438b

These makes merging branches & applying patches a hassle, while giving
minimal benifit, not even helping readability.

I recall this topic came up before but couldn't find it on the wiki
anywhere, so added a note:

http://wiki.blender.org/index.php/Dev:Doc/New_Committer_Info#Commit_.28Best_Practice.29

----
Don't make minor changes such as trailing whitespace to existing code
(unless you're the module owner).
----

... though this could be changed if other devs have a strong opinion.

-- 
- Campbell


More information about the Bf-committers mailing list