)]}'
{
  "commit": "e5d41a57e6a9e42e454ad9baf7cc3e1ab0926211",
  "tree": "30aa3b2a0564edccbab467e114791c93aae03a2c",
  "parents": [
    "be9a86f459f8e785bac42abcea5d13bd4ded251e"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Thu Feb 18 17:03:26 2021 -0500"
  },
  "committer": {
    "name": "CQ bot account: commit-bot@chromium.org",
    "email": "commit-bot@chromium.org",
    "time": "Fri Feb 19 16:24:54 2021 +0000"
  },
  "message": "Future-proof vs_toolchain.py for VS2019.\n\nIn trying to figure out an ARM64 builder issue, I tried VS2019. That\ndidn\u0027t fix the ARM64 issue, but it did reveal that I ported over some of\nthe logic from Chromium wrong. For \"new-style\" paths, the toolchain\ndirectory should be toolchain_data[\u0027path\u0027], not the parent directory of\nwin_sdk.\n\n(The latest VS2019 package in Chromium puts win_sdk a few directories\ndown from the toolchain root.)\n\nThis CL should be a no-op for now because all our current toolchains use\nChromium\u0027s \"old-style\" win_sdk-relative paths.\n\nChange-Id: I8ad7784abb479d1ede3995a44433e57448e8debf\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/45744\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c15df49c8f6bc9524057aec07a5a5716dcb8da89",
      "old_mode": 33188,
      "old_path": "util/bot/vs_toolchain.py",
      "new_id": "904f3ca711737f10c2d93e21df7b9be3774c1e26",
      "new_mode": 33188,
      "new_path": "util/bot/vs_toolchain.py"
    }
  ]
}