Good point on making separate commits for "whitespace" versus "content" We currently have pep8 (python style checker) as a git commit hook, and the first few t

Good point on making separate commits for "whitespace" versus "content" We currently have pep8 (python style checker) as a git commit hook, and the first few times we used it, we'd have 10 lines of legitimately modified code and then 100 lines of "style corrections." Usually I commit my changes first, and then do another pass with style changes. Maybe it would be easier if I did it the other way around - whitespace pull request first, followed by the actual change.