)]}'
{
  "commit": "9709ad52eb7cba2754256c66f4c7129cc6d244a7",
  "tree": "827425c7e2d8921e7ff24625ee47a2cc4b94990a",
  "parents": [
    "eec840da626eadebb43eba82c145abae308f81fc"
  ],
  "author": {
    "name": "Adam Langley",
    "email": "agl@google.com",
    "time": "Wed Oct 16 10:09:26 2019 -0700"
  },
  "committer": {
    "name": "CQ bot account: commit-bot@chromium.org",
    "email": "commit-bot@chromium.org",
    "time": "Wed Oct 16 21:25:03 2019 +0000"
  },
  "message": "Fix $OPENSSL_ia32cap handling.\n\nThe comment says that an \"0x\" prefix indicates a hex value. However we\nalways passed PRIu64 as the format specifier for |sscanf|, and |sscanf|\nisn\u0027t documented to handle an 0x prefix expect for \"i\"-family format\nspecifiers. With |PRIu64|, |sscanf| reads any leading \"0x\" as just zero.\n\nInstead, check for \"0x\" ourselves and use |PRIx64| if found to parse hex\nvalues.\n\nChange-Id: Id5ed7009d30902022e5ee640e8931bf1431dedc0\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/38264\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "832e9d6d7abf8cd4ff4b24e845df05d4a7c8b26e",
      "old_mode": 33188,
      "old_path": "crypto/cpu-intel.c",
      "new_id": "cc41fc47ff2d585dec7b1e12cac3cb4b691e57d1",
      "new_mode": 33188,
      "new_path": "crypto/cpu-intel.c"
    }
  ]
}