Changes between Version 15 and Version 16 of RFC4

Timestamp:

Mar 29, 2017, 6:40:31 PM (7 years ago)

Author:

mloskot

Comment:

Clarify no-style-auto-fix policy

RFC4

@@ -38 +38 @@
 The `clang-format` is straightforward to run and can support development workflow as standalone tool or as one of many editor integrations or other bespoke utilities (eg. `git cl format` [Chromium]).
 
-Although no means to enforce the default formatting style are proposed, currently used CI services (eg. Travis CI) may be employed as a post-commit safety valve - a clang-format lint failure as a compile break (eg. [https://github.com/mongodb/mongo/blob/master/buildscripts/clang_format.py clang_format.py] build script used by MongoDB).
+No automation of code reformatting is proposed. It would be treating the symptomps, no cause: developers not following the code formatting standard.
+
+Although no means to enforce the default formatting style are proposed, currently used CI services (eg. Travis CI) may be employed as a post-commit safety valve - a clang-format lint failure as a compile break (eg. [https://github.com/mongodb/mongo/blob/master/buildscripts/clang_format.py clang_format.py] build script used by MongoDB). Alternatively, a gatekeeper may be installed in SVN/Git, rejecting commits with code not conforming to the code formatting style.
 
 == Code Formatting Rules ==