)]}'
{
  "commit": "336f7bd0ed70f5ee2595463b6bd8dd277e90c833",
  "tree": "4854b1808bcda18221e097a69c993c4a0cf6137a",
  "parents": [
    "2810cbc7784e9a21e7001c31b65af94fd9ba7a5b"
  ],
  "author": {
    "name": "Shawn O. Pearce",
    "email": "sop@google.com",
    "time": "Sat Apr 18 10:39:28 2009 -0700"
  },
  "committer": {
    "name": "Shawn O. Pearce",
    "email": "sop@google.com",
    "time": "Sat Apr 18 10:39:28 2009 -0700"
  },
  "message": "Avoid git fork on the common case of repo not changing\n\nUsually repo is upgraded only once a week, if that often.  Most of\nthe time we invoke HasChanges on the repo project (or even on the\nmanifest project) the current HEAD will resolve to the same SHA-1\nas the remote tracking ref, and there are therefore no changes.\n\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "09a768fb4c62d37cbb9847032afc4b7b882d43f6",
      "old_mode": 33188,
      "old_path": "project.py",
      "new_id": "9f4512f69aa68f8e689d137701d65fe27dc37fb1",
      "new_mode": 33188,
      "new_path": "project.py"
    }
  ]
}