)]}'
{
  "commit": "ec287902e6517f0f7d11738f411d111c1ed06df1",
  "tree": "ee4b3071c42e75bbd4dd955b9b1535bc15e5cd0b",
  "parents": [
    "4d5bb68d58f12885ea06fb73d5e17d8c780c9ff8"
  ],
  "author": {
    "name": "Marc Herbert",
    "email": "marc.herbert@intel.com",
    "time": "Thu Oct 27 12:58:26 2016 -0700"
  },
  "committer": {
    "name": "Marc Herbert",
    "email": "marc.herbert@intel.com",
    "time": "Thu Oct 27 12:58:26 2016 -0700"
  },
  "message": "_CheckDirReference: log actual error before suggesting --force-sync\n\nA recent backward incompatible change created confusion and loss of\nproductivity and highlighted the very limited amount of information\nprovided when repo sync fails; merely recommending to --force-sync\nand blow-up git repos without any hint as to why. The addition of\nthis basic _error(...) call would have provided a clue and will in\nthe future.\n\nBUG\u003dIssue 232\nTEST\u003dsimulate a breakage similar to the ones reported at\n  https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-dev/2-0oCy_CX5s\n  cd .repo/projects/src/third_party/libapps.git/\n  file info; rm info; ln -s wronglink info\n  cd -\n  repo sync src/third_party/libapps/\n  # error message now shows the failure\n\nChange-Id: Idd2f177a096f1ad686caa8c67cb361d594ccaa57\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "29638ef7936220c3305ad39262068111e44ae1e2",
      "old_mode": 33188,
      "old_path": "project.py",
      "new_id": "bbb052a300060290117a3158f9caf7ceee42bcc9",
      "new_mode": 33188,
      "new_path": "project.py"
    }
  ]
}