)]}'
{
  "commit": "16d0abf5294cfae2696401d738ff2cb8d0808b52",
  "tree": "deea0646bf6a7b298679e470cce6d90ff8bc93b5",
  "parents": [
    "a3345c9b98cb965a8c28d13de6a9258d642492d6"
  ],
  "author": {
    "name": "Petr Hosek",
    "email": "phosek@google.com",
    "time": "Mon Oct 28 19:54:25 2019 -0700"
  },
  "committer": {
    "name": "Commit Bot",
    "email": "commit-bot@chromium.org",
    "time": "Wed Oct 30 03:32:48 2019 +0000"
  },
  "message": "Handle metadata walk_keys relative to the target directory\n\nDon\u0027t process relative labels relative to root, process them relative\nto the target directory.\n\nTo illustrate this, take the following example:\n\n//x:x\n//x:meta\n//x/z:z\n\nWhere x is a target that depends on z, and meta is a generated_file\ntarget that sets walk_keys to just \"z\", the collection would fail\nbecause generated_file would try to resolve \"z\" (which is a relative\npath) against the root (i.e. as //z:z). This patches changes the logic\nto always resolve the walk_keys against the target current directory,\ni.e. in case of //x:meta it\u0027ll be resolved against //x which is correct\nsince \"z\" is relative to that.\n\nBug: 117\nChange-Id: I4da2a3d5e279a970794cdf163f596d8c9a107f4b\nReviewed-on: https://gn-review.googlesource.com/c/gn/+/6380\nReviewed-by: Brett Wilson \u003cbrettw@chromium.org\u003e\nCommit-Queue: Brett Wilson \u003cbrettw@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "db7a1be774b5c433b7ef1f654c74984eaa35251f",
      "old_mode": 33188,
      "old_path": "tools/gn/target.cc",
      "new_id": "bc879285916b57cf2c29bfea9f803d982cd684b3",
      "new_mode": 33188,
      "new_path": "tools/gn/target.cc"
    },
    {
      "type": "modify",
      "old_id": "24f482225801fe2fd26b8bca97527b5d3d67728d",
      "old_mode": 33188,
      "old_path": "tools/gn/target_unittest.cc",
      "new_id": "93fc6a4ccd30a4d7143f358bc69fd05b121f98d9",
      "new_mode": 33188,
      "new_path": "tools/gn/target_unittest.cc"
    }
  ]
}