On Wed Feb 25 2015 at 9:15:38 AM James Peach <jpe...@apache.org> wrote:
> > > On Feb 24, 2015, at 1:59 PM, Leif Hedstrom <zw...@apache.org> wrote: > > > > Hi, > > > > clang-format has finally gotten to the point where we can get it to > format our code similar, but not quite identical, to what we have today. > Doing all formatting programmatically has several benefits: > > > > It’s no longer up to subjective or personal preferences, we’ll learn to > live and love the clang-format coding style. > > It can be automated. > > It can also be used as a tool for people who want to work / see code in > a different style, but commit in our standard style. > > > > > > I have updated the .clang-format files that is in our Git master, we > might need to do a few more tweaks, but it’s getting pretty close. It does > require a very recent version of clang-format, the one I used is > > > > clang-format version 3.6.0 (tags/google/testing/2015-01-13) > > Does this completely destroy code history? > > J The simple answer to this is: "No, we still use git." But what I think you are really asking is, "Does `git blame` become less useful?" While it's true that a simple `git blame` will show lots of format changes instead of what you may deem more useful, I would argue there are better ways to find what you are looking for anyway: http://jfire.io/blog/2012/03/07/code-archaeology-with-git/ Hope this helps.
