@pames *Only* since you're asking:

I hear you on the advantages of improving code formatting incrementally and leaving code better than you found it.

I think whitespace changes should *only* happen under two circumstances:
1. On lines of code that are being changed in a non-whitespace way anyway.
2. In commits consisting *only* of whitespace changes, which show as no changes at all in the commit when viewed ignoring whitespace ([`?w=1` on the GitHub URL viewing the commit](https://github.com/blog/967-github-secrets)).

So, here, I think it would be better not to include these whitespace changes in the same commit or even on the same pull request as the changeset that is substantially changing `mod_auth_cas` SSL configuration.

I also think that sometimes the "rip the bandaid approach" is the better way to go.  Consensus on whitespace conventions, one massive commit consisting exclusively of whitespace changes, and then ideally add editor style definition files or build automation / post-commit hook to enforce the whitespace convention to prevent regression, and be done.