)]}'
{
  "commit": "14a6674e32b3000dbe8b7c96b0d1bb4fb0021720",
  "tree": "024482226fefd4c188f20f56047325b69d388a9f",
  "parents": [
    "34acdd253439448b6c08c3abfc5e7b8bd03f383f"
  ],
  "author": {
    "name": "Brian Harring",
    "email": "ferringb@google.com",
    "time": "Fri Sep 28 20:21:57 2012 -0700"
  },
  "committer": {
    "name": "Brian Harring",
    "email": "ferringb@google.com",
    "time": "Fri Sep 28 22:31:27 2012 -0700"
  },
  "message": "manifest: record the original revision when in -r mode.\n\nCurrently when doing a sync against a revision locked manifest,\nsync has no option but to fall back to sync\u0027ing the entire refs space;\nit doesn\u0027t know which ref to ask for that contains the sha1 it wants.\n\nThis sucks if we\u0027re in -c mode; thus when we generate a revision\nlocked manifest, record the originating branch- and try syncing that\nbranch first.  If the sha1 is found within that branch, this saves\nus having to pull down the rest of the repo- a potentially heavy\nsaving.\n\nIf that branch doesn\u0027t have the desired sha1, we fallback to sync\u0027ing\neverything.\n\nChange-Id: I99a5e44fa1d792dfcada76956a2363187df94cf1\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8e9efd1375d0b9eca2441e73f416bed8d579cafe",
      "old_mode": 33188,
      "old_path": "manifest_xml.py",
      "new_id": "be185477d1d0cc38708eca078cb712f333ebb446",
      "new_mode": 33188,
      "new_path": "manifest_xml.py"
    },
    {
      "type": "modify",
      "old_id": "4621013ca23bed14e11df99dd93586706f769083",
      "old_mode": 33188,
      "old_path": "project.py",
      "new_id": "04c43bb76c2bc6835fb1680e15d7994e8b7ee1ab",
      "new_mode": 33188,
      "new_path": "project.py"
    },
    {
      "type": "modify",
      "old_id": "cd1965310ab24972458000f3f4ef8ab8e4624c79",
      "old_mode": 33188,
      "old_path": "subcmds/manifest.py",
      "new_id": "4388765466a9526426dd2abcfe7fcca90f4bdeaf",
      "new_mode": 33188,
      "new_path": "subcmds/manifest.py"
    }
  ]
}