The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fe53f360120731ef49a48a314f843694e40a8659

commit fe53f360120731ef49a48a314f843694e40a8659
Author: Lucas Garron <lgarron@chromium.org>
Date: Sat Dec 03 01:03:50 2016

Re-generate transport_security_state.h

Normally, regenerating this file is deterministic. I can't find a discrepancy between the JSON and the behaviour of the generated data, but this updates the .h so we can debug without blocking further changes right now.

BUG= 670139 
TBR=palmer@chromium.org

Review URL: https://codereview.chromium.org/2549903003 .

Cr-Commit-Position: refs/heads/master@{#436114}

[modify] https://crrev.com/fe53f360120731ef49a48a314f843694e40a8659/net/http/transport_security_state_static.h

This appears to have happened again. Running the generator on ToT results in a change to the binary data in the .h file.

Likely due to [1] missing the .h diff.

[1] https://chromium.googlesource.com/chromium/src/+/21f26e967e50357e2e251249a51b37920dff6236%5E%21/net/http/transport_security_state_static.json

yargh. I was pretty sure I ran it for both the M58 removals and additions, but there are a couple of reasons I might not have (e.g. rebasing mistake, other git mixups, or just plain forgetting). Thanks for pointing this out.

Actually, let's make that a separate issue:  Issue 701148