)]}'
{
  "commit": "8ced8641c88d37891a46d42ac1805e380ef6c377",
  "tree": "bb32899a9865ae64a269576598bcc801b69bbcf7",
  "parents": [
    "2536f806258ce2038eea73269290559906cab99a"
  ],
  "author": {
    "name": "Doug Anderson",
    "email": "dianders@google.com",
    "time": "Mon Jan 10 14:16:30 2011 -0800"
  },
  "committer": {
    "name": "Shawn O. Pearce",
    "email": "sop@google.com",
    "time": "Tue Feb 01 09:57:29 2011 -0800"
  },
  "message": "Renamed \u0027repo_hooks\u0027 function to \u0027_ProjectHooks\u0027.\n\nThis renaming was done for two reasons:\n1. The hooks are actually project-level hooks, not repo-level\n   hooks.  Since we are talking about adding repo-level hooks,\n   It keeps things less confusing if we name the existing hooks\n   to be \"ProjectHooks\"\n2. The function is a private function in project.py and so\n   should have capitalization to match.\n\nI also added a docstring describing this function.\n\nChange-Id: I1d30f5de08e8f9f99f78146e68c76f906782d97e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ca092b89bc9536dc46c05c10e53889f29a7ef5e8",
      "old_mode": 33188,
      "old_path": "project.py",
      "new_id": "125fb48c631acc711f51f4f791a72232fb797995",
      "new_mode": 33188,
      "new_path": "project.py"
    }
  ]
}