)]}'
{
  "commit": "fa99799583dfc3b485012dd0575287643f568b72",
  "tree": "8bde1e2205ef987181a1bbbb1c8f33fbd29e402d",
  "parents": [
    "55f01c3c338166f2ca7e67ae5d6c3ae6b7ac75c4"
  ],
  "author": {
    "name": "Serge Bazanski",
    "email": "serge@nexantic.com",
    "time": "Tue Mar 23 17:29:42 2021 +0100"
  },
  "committer": {
    "name": "Leopold Schabel",
    "email": "leo@nexantic.com",
    "time": "Thu Apr 01 18:58:25 2021 +0200"
  },
  "message": "third_party/qemu: better explain tb_invalidate_phys_range patch\n\nAt a glance, this change looks somewhat scary, and might be interpreted\nas an attempt to backdoor qemu.\n\nThis better explains what\u0027s going on, and adds an extra always-firing\nassert to prove that there\u0027s nothing up our sleeves, and that this\nbranch should never be taken in the first place.\n\nTest Plan: Refactor, should be covered by tests.\n\nX-Origin-Diff: phab/D744\nGitOrigin-RevId: c86638cf9e90041d2ad19d26715c7d4dd5a43e98\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "af1ba5f2979da44814baa36a1944ae225d9f9449",
      "old_mode": 33188,
      "old_path": "third_party/qemu/patches/fix_code_issues.patch",
      "new_id": "cffc41b443a20cc68e26a6ab1cae158c25de4d4e",
      "new_mode": 33188,
      "new_path": "third_party/qemu/patches/fix_code_issues.patch"
    }
  ]
}