)]}'
{
  "commit": "235ee97b469ca6761e5096ea829f4da032c591fe",
  "tree": "fed99f1e5659b01de329513838328f7319d00fd8",
  "parents": [
    "5a3eb9ea7e787b7a787b7a6529d181d7e1fdb54e"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Fri Sep 01 10:39:44 2023 -0400"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Fri Sep 01 17:26:06 2023 +0000"
  },
  "message": "Reland \"Build with C11 on MSVC in the standalone Bazel build\"\n\nThis reverts 1e2f1696636088626cb223aa5a10f64e07b62ffd. Bazel 6.3 has\nsince been released, which includes a fix for\nhttps://github.com/bazelbuild/bazel/issues/15073. Envoy and gRPC have\nboth since updated to this Bazel version. The policies in\nhttps://opensource.google/documentation/policies/cplusplus-support#build_systems\nalso imply a minimum Bazel version of 6.3.2.\n\nI\u0027m thinking we let this bake for a little while, to catch any\nunexpected issues, and then, if it sticks, we try to go ahead and\nrequire C11 across the board.\n\nUpdate-Note: If using Bazel with MSVC, and the build fails with\nsomething like \"Command line error D8016 : \u0027/std:c++20\u0027 and \u0027/std:c11\u0027\ncommand-line options are incompatible\", you are likely running into the\nabove Bazel bug. Update to Bazel 6.3 or later.\n\nBug: 623, 624\nChange-Id: I8baa99392ca47bc7580bc2930e7f4b16beced91e\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/62905\nAuto-Submit: David Benjamin \u003cdavidben@google.com\u003e\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\nCommit-Queue: Adam Langley \u003cagl@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f5bbbdc51a0a07ad89a1d825abfd50dc53571f74",
      "old_mode": 33188,
      "old_path": "util/BUILD.toplevel",
      "new_id": "48dc9206837e7cdc0bc295708041a34b6622cbf9",
      "new_mode": 33188,
      "new_path": "util/BUILD.toplevel"
    }
  ]
}