)]}'
{
  "commit": "2bac1f81c1a55f99c887ef7e6e0dc717c0339e68",
  "tree": "a19c89b05ff2ce1591c5927a9462a48551005dec",
  "parents": [
    "8b8cb2d4085ebc209463b2503f33b8c1716603f9"
  ],
  "author": {
    "name": "Jiyong Park",
    "email": "jiyong@google.com",
    "time": "Tue Apr 05 14:03:34 2022 +0900"
  },
  "committer": {
    "name": "Jiyong Park",
    "email": "jiyong@google.com",
    "time": "Tue Apr 05 14:07:48 2022 +0900"
  },
  "message": "Deprecate \"/apex/\u003cname\u003e/ld.config.txt\n\nThe file is a manually created linker config file for the binaries in\nthe APEX. This is discouraged since such a manually created linker\nconfig is error-prone and hard to maintain. Since the per-APEX\nlinker config file is automatically created by the linkerconfig tool as\n/linkerconfig/\u003cname\u003e/ld.config.txt, we can safely deprecated the\nfallback path.\n\nThere currently are two APEXes using these hand-crafted configs. They\ncan (and should) keep the configs for backwards compatibility; in case\nwhen they run on older devices where the auto-generated configs are not\navailable. But for newer platforms, the files are simply ignored and no\nnew APEX should be using that.\n\nBug: 218933083\nTest: m\nChange-Id: I84bd8850b626a8506d53af7ebb86b158f6e6414a\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3488f5cc716eaef3c7ead6cdff7f0390e7ed9e56",
      "old_mode": 33188,
      "old_path": "linker/linker.cpp",
      "new_id": "c6588d2cd4718ac0c8cdca35513428d72f6c2979",
      "new_mode": 33188,
      "new_path": "linker/linker.cpp"
    }
  ]
}