)]}'
{
  "commit": "8c0a6ebfc245bdbb3d7315cf8a47b91e4326fa44",
  "tree": "6702fe2b4b886153ab2340932b75eb24280f3d6a",
  "parents": [
    "83b74c6a7a1ad33792be3adf10820ae287de8c40"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Thu Jul 16 14:45:51 2020 -0400"
  },
  "committer": {
    "name": "Adam Langley",
    "email": "agl@google.com",
    "time": "Thu Jul 16 19:32:10 2020 +0000"
  },
  "message": "Add a JSON output to generate_build_files.py.\n\ngRPC are currently importing generate_build_files.py, injecting a\ncustom printer, and running into problems with the symlinks they set up\nto make this work, as well as needing to delete duplicate generated\nfiles.\nhttps://github.com/grpc/grpc/blob/53a5ad34c0b5fca2cc9fd9ec4b354ff79c12948b/src/boringssl/gen_build_yaml.py#L130\nhttps://boringssl-review.googlesource.com/c/boringssl/+/42164\n\nRather than layer on more hacks, add a JSON output to\ngenerate_build_files.py. This outputs a sources.json file that folks\nwith especially custom builds can consume. (Looks like gRPC converts to\nsome home-grown YAML format which I imagine is further processed by some\nother generator?) We can then add it to master-with-bazel\u0027s output.\n\nChange-Id: I82b4ea0647386ca6c76a977f057b9962f40d41c8\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/42204\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6c3977d40f2f9d33ef3bc36ad9e493f5fc3f4eb6",
      "old_mode": 33188,
      "old_path": "util/generate_build_files.py",
      "new_id": "793652875e4505a43df72141606f5004631fc918",
      "new_mode": 33188,
      "new_path": "util/generate_build_files.py"
    }
  ]
}