)]}'
{
  "commit": "126e298214df0ce364b9dae0aec12b7b02f627ce",
  "tree": "0a11ceb83a40dd2d7f5353cab84ac81d0269b87b",
  "parents": [
    "24245e00946b43d086d8bd55cf4facd00479959a"
  ],
  "author": {
    "name": "John L. Villalovos",
    "email": "john.l.villalovos@intel.com",
    "time": "Thu Jan 29 21:58:12 2015 -0800"
  },
  "committer": {
    "name": "John L. Villalovos",
    "email": "john.l.villalovos@intel.com",
    "time": "Tue Feb 03 13:49:51 2015 -0800"
  },
  "message": "Handle case where \u0027git remote prune\u0027 needs to be run\n\nHandle the case when this error occurs:\n    error: some local refs could not be updated; try running\n     \u0027git remote prune origin\u0027 to remove any old, conflicting branches\n\nThis is usually caused by a reference getting changed from a file to a\ndirectory.\n\nFor example:\n  Initially someone creates a branch \u0027foo\u0027 and it is stored as:\n    .git/refs/remotes/origin/foo\n\n  Then later on it is decided to change the layout structure where \u0027foo\u0027\n  is a directory with branches below it:\n    .git/refs/remotes/origin/foo/master\n\n  The problem occurs when someone still has\n  \u0027.git/refs/remotes/origin/foo\u0027 on their system and does a repo sync.\n  When this occurs the error message for needing to do a\n  \u0027git remote prune origin\u0027 occurs.\n\nNow when doing a \u0027git fetch\u0027 if the error message from git says that a\n\u0027git remote prune\u0027 is needed, it will do the prune and then retry the\nfetch.\n\nChange-Id: I4c6f5aa6bd932f0ef7a39134400bedd52e82f633\nSigned-off-by: John L. Villalovos \u003cjohn.l.villalovos@intel.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4e9dba7fa64a9910fe70ec01b1d3e2d980de8479",
      "old_mode": 33188,
      "old_path": "project.py",
      "new_id": "319a710fd429ad5f2fee202b8f8cf5c6f0271930",
      "new_mode": 33188,
      "new_path": "project.py"
    }
  ]
}