Changes between Version 16 and Version 17 of RFC4

Timestamp:

Mar 29, 2017, 6:43:14 PM (7 years ago)

Author:

mloskot

Comment:

Add git blame -w

RFC4

@@ -116 +116 @@
 The proposal recommends to just do one big reformat of the codebase.
 
-While it may seem causing clutter in the repository log (eg. `svn blame`), if it occurs infrequently (eg. yearly) and is applied to the entire codebase at that time, it should not be very disruptive to the source code history. 
+While it may seem causing clutter in the repository log (eg. `svn blame`), if it occurs infrequently (eg. yearly) and is applied to the entire codebase at that time, it should not be very disruptive to the source code history. One way to cope with skewed history is to use `git blame -w` which ignores whitespace when comparing commits.
 
 Partial application of the code formatting rules would create more work without delivering the full benefit [MongoDB] leading to codebase with different styles mixed.