> 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