//third_party/WebKit clang-format preparation patch

third_party/WebKit/Source/core/layout/ng/.clang-format

-# Defines the Chromium style for automatic reformatting.
-# http://clang.llvm.org/docs/ClangFormatStyleOptions.html
-BasedOnStyle: Chromium
-# This defaults to 'Auto'. Explicitly set it for a while, so that
-# 'vector<vector<int> >' in existing files gets formatted to
-# 'vector<vector<int>>'. ('Auto' means that clang-format will only use
-# 'int>>' if the file already contains at least one such instance.)
-Standard: Cpp11

[cbiesinger, 2016/09/29 20:39:08]

As one of the layout/ng engineers: Can we keep ReflowComments as true for this
directory?

[Nico, 2016/09/29 20:46:09]

Sure. I think the way we're going to roll out comment formatting is to manually
reflow comments per directory and add a . clang-format in each dir that's done,
so we can just put that here if the comments here are already short. (Note that
clang-format's comment reflowing really is unusably bad, you'll always want to
manually do this)

For organizational reasons we'll probably delete this file and add it back right
after the reformatting if that's cool.

[danakj, 2016/09/29 20:54:04]

If BasedOnStyle: Chromium means all the comments in here are 80 cols then
keeping ReflowComments makes sense. Same for other cases.

[dcheng, 2016/09/29 21:10:58]

We'll reland this afterwards, but for the giant commit, it's a bit safer to just
delete any nested .clang-formats and reland any that are still desired after the
reformat. The idea is to prevent any interesting surprises in the giant commit
(which we've been testing).

Does this sound reasonable to you?

[danakj, 2016/09/29 21:19:56]

Yes