)]}'
{
  "commit": "44a2a2fcab63071375841d7a5001dd301ebac194",
  "tree": "8f28e4e1222a0fc25b6e8fced358b000eef88e6b",
  "parents": [
    "761a6275d4b7089db50dda22eb4241ba7f923769"
  ],
  "author": {
    "name": "Harvey Tuch",
    "email": "htuch@google.com",
    "time": "Thu Jun 21 13:05:27 2018 -0400"
  },
  "committer": {
    "name": "Harvey Tuch",
    "email": "htuch@google.com",
    "time": "Thu Jun 21 13:57:31 2018 -0400"
  },
  "message": "json: include field name in InvalidName status messages.\n\nThis is invaluable for chasing down the culprit in failed JSON -\u003e proto\nconversions. We often see in Envoy that a failed JSON (or indirectly via\nYAML) configuration won\u0027t load but it\u0027s unclear why.\n\nSigned-off-by: Harvey Tuch \u003chtuch@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f81a7a306172853fa18b9604729a5860b6bf575a",
      "old_mode": 33188,
      "old_path": "src/google/protobuf/util/json_util.cc",
      "new_id": "dd8c61110510d02477f0c6a4267caa5d436612af",
      "new_mode": 33188,
      "new_path": "src/google/protobuf/util/json_util.cc"
    }
  ]
}