)]}'
{
  "commit": "c325dc35f621fe24d0460bb14547cdb51e00c00b",
  "tree": "9154d75a5a5348609fc3b6d637871298c831b407",
  "parents": [
    "f322b9abb4cadc67b991baf6ba1b9f2fbd5d7812"
  ],
  "author": {
    "name": "Shawn O. Pearce",
    "email": "sop@google.com",
    "time": "Mon Oct 03 08:30:24 2011 -0700"
  },
  "committer": {
    "name": "Shawn O. Pearce",
    "email": "sop@google.com",
    "time": "Mon Oct 03 08:30:24 2011 -0700"
  },
  "message": "sync: Fetch after applying bundle and retry after errors\n\nAfter a $GIT_URL/clone.bundle has been applied to the new local\nrepository, perform an incremental fetch using `git fetch` to ensure\nthe local repository is up-to-date. This allows the hosting server\nto offer stale /clone.bundle files to bootstrap a new client.\n\nIf a single git fetch fails, it may succeed again after a short\ndelay.  Transient failures are typical in environments where the\nremote Git server happens to have limits on how many requests it\ncan serve at once (the anonymous git daemon, or an HTTP server).\nWait a randomized delay between 30 and 45 seconds and retry the\nfailed project once.  This delay gives the site time to recover\nfrom a transient traffic spike, and the randomization makes it less\nlikely that a spike occurs again from all of the same clients.\n\nChange-Id: I97fb0fcb33630fb78ac1a21d1a4a3e2268ab60c0\nSigned-off-by: Shawn O. Pearce \u003csop@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5adfe82ead1cc27df2cdc1385a33e8300a3222e3",
      "old_mode": 33188,
      "old_path": "project.py",
      "new_id": "43f4713cf44a20b90e739e4b744143387705b322",
      "new_mode": 33188,
      "new_path": "project.py"
    }
  ]
}