)]}'
{
  "commit": "6c5944606af3c52626745b5256e9e5f0d5c362a2",
  "tree": "a34387f91d0a67c01455c2a211ae5401fe5a2bda",
  "parents": [
    "eceeb1b1f5edb0f42e690bffdf81828abd8ea7fe"
  ],
  "author": {
    "name": "Aymen Bouaziz",
    "email": "aymen.bouaziz@parrot.com",
    "time": "Tue Oct 25 18:03:51 2016 +0200"
  },
  "committer": {
    "name": "Aymen Bouaziz",
    "email": "aymen.bouaziz@parrot.com",
    "time": "Fri Oct 28 14:29:57 2016 +0200"
  },
  "message": "Fix checkout error when depth passed to repo init and revision is a sha1\n\nCurrently, if direct fetch of a sha1 is not supported by git server and\ndepth option is used, we fallback on syncing the upstream branch by\nignoring depth option.\n\nThis fallback doesn\u0027t work in next 2 cases:\n(1) upstream attribute is not specified in manifest\n(2) depth option is passed to repo init command\n    (not with clone-depth attribute in manifest)\n\nThis commit do the following:\n- fixes (1) by updating condition used to apply fallback\n  first we retry with depth set to None, then by syncing all branches\n- fixes (2) by passing depth as argument of _RemoteFetch() method\n  thus, its value is not set again to depth value passed to repo init\n  command when applying fallback\n\nChange-Id: Ifd6fffafc49ba229df624b0d7b64c83d47619d17\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "142258e4b789134c42607e6dc9a379fdfc0465ab",
      "old_mode": 33188,
      "old_path": "project.py",
      "new_id": "cdb61c2186e77a7600b1f2281570b38417fda629",
      "new_mode": 33188,
      "new_path": "project.py"
    }
  ]
}