On Tue Feb 24 2015 at 2:59:52 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) > > > This I installed on my OS X laptop, using HomeBrew. > > Finally, Phil Sorber (the PM for the 5.3 LTS) has requested that we do > this before he branches for 5.3. So, assuming we agree to do this, we have > to make a decision asap. If you have objections to this proposal, please > discuss that here now. > > Just to clarify, I'd like to see this happen pre-branch so that back ports have less conflicts. 5.2.x will be deprecated as soon as 5.3.0 is released and Leif is doing a 5.2.1 release before we format and branch for 5.3. 4.2.x will be tougher to backport to, but as time goes on there will be less backports for it and it would be harder to backport to anyway. > Thanks, > > — Leif and Phil
