Format HpackEntry initializer lists.

Format HpackEntry initializer lists.

This is a follow-up to https://crrev.com/2663203002.  While
https://crrev.com/2663203002 is properly formatted, it turns out that the
internally used clang-format is stricter.  This CL changes formatting to a style
that is accepted by both Chromium's clang-format and the internal one.

BUG=680056
Review-Url: https://codereview.chromium.org/2718093002
Cr-Commit-Position: refs/heads/master@{#453340}
Committed: https://chromium.googlesource.com/chromium/src/+/a73f729a9a20ca911ced2e9896bf3c5aad95fe27

[Bence, 2017-02-27 15:00:34]

The CQ bit was checked by bnc@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-02-27 15:00:49]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-27 16:00:14]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-02-27 16:00:15]

Dry run: This issue passed the CQ dry run.

[Bence, 2017-02-27 16:24:16]

bnc@chromium.org changed reviewers:
+ rch@chromium.org

[Bence, 2017-02-27 16:24:17]

Ryan: PTAL.  I knew that Chromium's git cl format might allow either of multiple
alternatives in certain cases, but I didn't know that the internal clang-format
does not accept everything that Chromium's does.  I might try to make Chromium
rules stricter for shared directories.

[Ryan Hamilton, 2017-02-27 19:44:15]

LGTM. I'm surprised that chromium's format allowed those. *head explodes*

[Bence, 2017-02-27 21:05:55]

The CQ bit was checked by bnc@chromium.org

[commit-bot: I haz the power, 2017-02-27 21:06:22]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-27 21:17:22]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1488229555148400, "parent_rev":
"29670c02097672438f970b0b75f5b20470d75544", "commit_rev":
"a73f729a9a20ca911ced2e9896bf3c5aad95fe27"}

[commit-bot: I haz the power, 2017-02-27 21:18:02]

Description was changed from

==========
Format HpackEntry initializer lists.

This is a follow-up to https://crrev.com/2663203002.  While
https://crrev.com/2663203002 is properly formatted, it turns out that the
internally used clang-format is stricter.  This CL changes formatting to a style
that is accepted by both Chromium's clang-format and the internal one.

BUG=680056
==========

to

==========
Format HpackEntry initializer lists.

This is a follow-up to https://crrev.com/2663203002.  While
https://crrev.com/2663203002 is properly formatted, it turns out that the
internally used clang-format is stricter.  This CL changes formatting to a style
that is accepted by both Chromium's clang-format and the internal one.

BUG=680056

Review-Url: https://codereview.chromium.org/2718093002
Cr-Commit-Position: refs/heads/master@{#453340}
Committed:
https://chromium.googlesource.com/chromium/src/+/a73f729a9a20ca911ced2e9896bf...
==========

[commit-bot: I haz the power, 2017-02-27 21:18:03]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/a73f729a9a20ca911ced2e9896bf...

[Bence, 2017-02-27 22:53:39]

On 2017/02/27 19:44:15, Ryan Hamilton wrote:
> LGTM. I'm surprised that chromium's format allowed those. *head explodes*

I'm surprised too.  What's even more confusing is the following: if I locally
revert https://crrev.com/2663203002, then re-land, then reset commit, then
stage, then run git cl format, then it does not make any modifications.  In
other words, https://crrev.com/2663203002 is properly git cl formatted. 
However, if I revert this CL locally, then reset commit, then stage, then run
git cl format, then git cl format really does not the change, and reverts the
revert entirely.  Something is not working right, or I am holding it all wrong.