)]}'
{
  "commit": "abaa7f312f1b6c8d11d7c757fe909900ce5788b5",
  "tree": "2eba7244f267c9df33510a820b5353da1d7722cd",
  "parents": [
    "7cccfb2cf0ed1ed14f6b8a5bdb36459ebcb4db5a"
  ],
  "author": {
    "name": "Kevin Degi",
    "email": "kdegi@codeaurora.org",
    "time": "Wed Nov 12 11:27:45 2014 -0700"
  },
  "committer": {
    "name": "Kevin Degi",
    "email": "kdegi@codeaurora.org",
    "time": "Wed Jul 29 14:44:46 2015 -0600"
  },
  "message": "Add option to correct gitdir when syncing\n\nIn some cases, a user may wish to continue with a sync even though\nit would require overwriting an existing git directory. This behavior\nis not safe as a default because it could result in the loss of some\nuser data, but as an optional flag it allows the user more flexibility.\n\nTo support this, add a --force-sync flag to the sync command that will\nattempt to overwrite the existing git dir if it is specified and the\nexisting git dir points to the wrong obj dir.\n\nChange-Id: Ieddda8ad54e264a1eb4a9d54881dd6ebc8a03833\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9e8ee8682e973f1ba8c3355e69f42b94374234e7",
      "old_mode": 33188,
      "old_path": "project.py",
      "new_id": "868425cea407d400e8a0b51f71bdaf84c545b6a2",
      "new_mode": 33188,
      "new_path": "project.py"
    },
    {
      "type": "modify",
      "old_id": "ec333ae7096b850fe028f5ac04f47b0a97326af7",
      "old_mode": 33188,
      "old_path": "subcmds/sync.py",
      "new_id": "a8074a4082c12a4d7ea292993f01d4264a5422f9",
      "new_mode": 33188,
      "new_path": "subcmds/sync.py"
    }
  ]
}
